PostgreSQL as a temporal database
Postgres 18 introduced temporal keys (WITHOUT OVERLAPS, PERIOD).Postgres 19 expands (UPDATE/DELETE ... FOR PORTION OF) temporal capabilities further.
Postgres 18 introduced temporal keys (WITHOUT OVERLAPS, PERIOD).Postgres 19 expands (UPDATE/DELETE ... FOR PORTION OF) temporal capabilities further.
Read, filter, and search your PostgreSQL logs for any branch in the Xata console or the CLI. Per-branch, per-instance, no log drain to set up.
What's new in pgstream v1.1.0: env vars in YAML config, JSON logs, Kubernetes health probes, custom TLS for OpenSearch, and fixes for composite primary keys.
See how we reduced branching times from 20+ seconds to around a second and what use-cases these speed improvements enable.
We've rebuilt the query editor from the ground up. The new version is faster, smarter, and easier to use.
How we rebuilt Xata's PostgreSQL branch metrics on a self-hosted VictoriaMetrics stack in six weeks, with zero user-visible downtime.
Build production-ready AI apps with Xata, Claude Code and Postgres workflows for safe migrations, branching and anonymized data cloning.
Every Xata Postgres branch includes a built-in PgBouncer pooler in transaction mode. Tuned for serverless and edge, scales to zero with the branch.
Read the technical details of our new distributed storage system, which is the key to scaling to a huge number of Postgres instances.
AI can write the code, but humans still need to own the engineering. A practical guide to using AI without drowning in slop.
Product managers and marketers are now submitting code with AI. Here's how to write PRs that engineers actually want to review, approve, and merge.
This spring, the Xata team gathered in the idyllic French countryside, where time slows down and nature provides the backdrop for conversation to flow. The setting left room for things to happen on their own, without the need to schedule too tightly. Here's how the week unfolded.
Use your existing Postgres. Run it better with Xata.