Recent releases from organizations and products in the Database category.
A proposed option lets a message be retried immediately, bypassing the configured retry delay. Messages otherwise retry per the configured policy, with the interval set by the Upstash-Retry-After header or an exponential-backoff default when the header is absent.
An option lets a step bypass the configured retry delay and retry immediately, while retries otherwise follow the retry policy's retryAfter duration expression or default exponential backoff calculation. The change targets critical or time-sensitive operations that need rapid reprocessing of specific steps or workflow runs.
Neon1A new storage_object_created trigger invokes a Neon Function when an object is created in an Object Storage bucket, passing the bucket name and object key in the POST body and supporting an optional key prefix to scope it to a path. Functions are long-running and remain compatible with scale to zero, and the schedule trigger is also available.
Neon2Neon Functions now support custom domains, replacing the Neon invocation URL with a branded hostname registered from the Console, CLI, SDK, or API. Domains are attached to one Function on one branch, and TLS certificates are provisioned automatically through Let's Encrypt.
Function Triggers let a branch-scoped cron schedule invoke a deployed Neon Function, keeping the timer outside the Postgres compute so scale to zero can stay on, unlike pg_cron. Triggers run JavaScript or TypeScript that can call HTTP, Object Storage, and the AI Gateway, and child branches inherit parent triggers disabled until enabled.
An existing MySQL database can now be attached as an external keyspace on a Vitess production branch, with PlanetScale running an external tablet against that source so it can be queried through Vitess without importing data first. External keyspaces can be created from the Clusters page on production branches or via the pscale keyspace create-external CLI command.
Neki extensions can now be enabled by name and configured with parameters in a single Terraform or pscale CLI update, with the extension list replacing the currently enabled set. Existing configurations that set preload libraries directly still work, but extensions cannot be combined with shared_preload_libraries or session_preload_libraries.
