Two new per-branch settings in Xata: 1. Postgres minor version upgrades. Pick your target in the UI or CLI, the API validates it, branch restarts. 2. Password rotation. `xata branch rotate-password` generates a new password, active in under 1 second. Existing connections keep working.

Code review is a negotiation. The submitter trades shipping speed for the reviewer's confidence that this won't cause pain later. Most new coders don't realize this. They optimize for "does it work" when they should optimize for "can my reviewer approve this safely."

Remote teams don’t get stronger from more meetings. They get stronger from time together that feels human. At Xata, Club Xata France 2026 was built around good conversations, shared meals, walks, and the unplanned moments in between. Check the full story here: xata.io/blog/club-xa...

Xata is now open source. Apache 2.0. Postgres platform with Copy-on-write branching at the storage layer. Copy a TB-sized database in seconds. Inactive copies scale to zero automatically. 100% vanilla Postgres.

Built our product analytics warehouse in vanilla Postgres instead of adding an OLAP stack. Four data sources (Keycloak, PostHog, Orb, internal DB), materialized views to flatten JSONB, pg_cron for refreshes, and database branches to iterate on the schema safely: xata.io/blog/postgre...

Our CTO Tudor Golubenco is speaking tonight at the PostgreSQL Berlin Meetup, hosted at Zalando. The talk: How we reduced CloudNativePG wake-up times from 20+ seconds to sub-second for Xata's scale-to-zero Postgres clusters. 20:15 CET if you're in Berlin: meetup.com/postgresql-m...

pgstream v1.0.0 is out, with a major architectural change. Schema changes are now emitted directly into WAL as logical messages, without schema logs or stored schema state. If you work with Postgres CDC, this might be interesting. Details in the blog 👇 xata.io/blog/pgstrea...

Did you know Postgres lets you put **constraints on domains**, not just tables? A domain is a custom data type with rules attached, and Postgres stores those CHECK constraints right in `pg_constraint` linked by `contypid` instead of `conrelid`. A clean way to centralize data rules 👌

Taking database snapshots and moving large volumes of data over the network is something our customers do regularly. While batching is the de facto way to make this efficient choosing the right batch size is non-trivial considering network variability, latency & system load. Read how we solved it👇🏽

@divyendusingh.com is doing a great job making agents do all sorts of stuff using databases. In our case with a few simple instructions, they are able to do branching operations, run queries, validate bug fixes and more. The blog posts are paired with demo videos, have a look 👀 👇🏽

New in xata clone: AI-assisted PII removal config (schema → strict config → validated).

New in xata clone: xata clone config --mode=ai Feed it your schema + prompt → get a strict, reviewable anonymization config that’s typically more complete than static heuristics. Blog post: xata.io/blog/smarter...

AI agents get useful faster with guardrails, not plugins. Repo playbook: gh issue → xata branch create + xata branch wait-ready → xata branch url (not $DATABASE_URL) → psql repro/verify → fix. Video + write-up:

Batching is often used to process large volumes of data but a batch size that works in one network setup can perform poorly in another. We applied automatic batch size tuning to Postgres snapshots in pgstream to adapt across different network environments. Check the post 👇 xata.io/blog/postgre...

PostgreSQL stores *all* constraints: check, not-null, PK, FK, unique, exclusion and domain constraints as rows in `pg_constraint` catalog. In Postgres 18, even NOT NULL constraints now get their own entries here (before 18 they lived in `pg_attribute`!).

Moving a production DB is stressful. Don’t. Keep prod on your infra. Stream a logical replica (WAL) into Xata, anonymize PII at ingest, then spin up copy-on-write Postgres branches in seconds - one per PR 👇

Testing one last change on prod before the holidays…

You wouldn’t let Claude Code touch prod. But some bugs *need* real data to reproduce. Here’s how we teach Claude to debug safely using Xata database branches 👇

It’s Friday and you want to ship to prod.

Giving agents access to realistic data via branches should scale the feature development without increasing costs. This shows how you can use the “scale to zero” feature of the Xata platform to improve feature development while keeping costs in check.

Postgres constraints are the rules that keep your data clean. Types tell you *what* can be stored but constraints enforce *what must be true*. If a row violates a rule, Postgres rejects it. No silent corruption. A few well-chosen constraints prevent entire classes of bugs. xata.io/blog/constra...

AI agents are “clever” to use available tools like grep, sed to find the relevant code files based on a prompt. Here we experiment with giving AI agent tools to change environment variables in a repository that it checked out and it worked.

We explored giving AI agents access to compute (via Sandbox) and database via Xata branches and some “commandments” to follow a developer-like workflow.

Can an AI Agent follow the same workflow that human developers can? We explored giving AI agent access to the database branch, a compute sandbox to execute code and instructions to follow a developer workflow (in plain English) and the experiment was a success.

Sometimes the right fix isn’t a workaround, but going upstream. After 6 months of work, @SferaDev from Xata landed our biggest contribution yet to Keycloak: persistent Organization invitations. Now merged, shipping in 26.5.0 🎉 Full write-up here 👇

Using Neovim with Claude Code? Xata engineer @richardgill.org shares a practical setup to: - See agent-written changes instantly - Reload git diffs in real time - Yank code with file locations so Claude gets proper context 📝 Tips for configuring Neovim for Claude Code xata.io/blog/configu...

pgstream v0.9.0 is live! This release improves schema replication, adds snapshot index progress tracking, supports more cloud providers, introduces reconnection retries, integrates with PostgreSQL Anonymizer and includes memory improvements. Big thanks to our community contributors 💜

Club Xata Rome 2025: our biannual reset. We traded Zoom for a shared table and left with sharper plans + stronger bonds.

Day 1 at #PGConfEU kicked off with Community Summits! Our own Gülçin Yıldırım Jelínek is co-organizing two of them ☸️ PostgreSQL on Kubernetes Summit 🧠 PostgreSQL & AI Summit Big thanks to the volunteers & speakers who made this happen. Community is what makes Postgres great 💙

The countdown to #PGConfEU is on ⏳ On Oct 21, @apatheticmagpie is co-hosting two community summits: 🧠 PostgreSQL & AI with Gulcin on DB Agents ☸️ PostgreSQL on Kubernetes with Esther Minano & Andrew Farries

Branch settings, faster. We reorganized the page and added search. What changed Search to jump directly to a setting. Logical groups with clear labels. Guardrails to reduce misclicks. Why it helps Quicker navigation. Less guessing, safer edits. Want early access? Ping us and we’ll enable it.

See write latency and replica lag before users do. New performance charts surface: WAL sync time → time to flush WAL to disk (disk/flush latency). Replication lag → how far a standby is behind the primary (freshness). Want early access? Ping us and we’ll switch it on for your account.

Project-level default database now live in Xata. Set one default and we point new connection strings, views, and child branches to it by default. Fewer misroutes and accidental writes to secondary DBs; faster onboarding. Set it in Project Settings → Default database. You can override per branch.

Create a Postgres branch in one screen. Name it → get the branch → run queries. No org/project setup first. Sane defaults now, easy rollback later. Want early access? Ping us and we’ll enable it.

Getting paged at 3 a.m + database operations ≠ heroics. At Berlin Postgres Meetup (Sep 23) we showed our open-source Xata Agent: Autonomously find slow queries, proposes safe fixes, runs on a schedule w/ approvals. As if you have a new database expert colleague. Recap:

Preload extensions once, use them everywhere. Set shared_preload_libraries at the branch level and every database on that branch shares the same foundation. Example: pg_stat_statements, pg_trgm → consistent query stats + text ops across envs. Notes: applies to all DBs on the branch.

PostgreSQL 18 is supported on Xata. Try PG18 in a safe, branch-based workflow: How to start: • Clone with anonymization → test on look-alike data. • Create a PG18 branch → run queries and migrations. • When ready, promote with pgroll for zero-downtime changes.

Thinking about changing your data model? View your schema as a table or UML diagram. When you are ready, use xata roll to apply changes without downtime.

PostgreSQL 18 is here 🎉 🐘 • Async I/O (io_uring/worker), faster reads • More index hits (skip scan, OR) • uuidv7(), virtual generated cols • OAuth2; Ask for Xata access and try PostgreSQL 18.

Shipping Text to SQL you can trust isn’t just prompting. It’s engineering for simplicity. At Xata we use a tiny context, pass schema + current SQL, a focused system prompt, and the right model per task. Fewer moving parts, cleaner UX. Build notes → xata.io/blog/how-we-...

Just dropped: pgstream v0.8.2 🛠️ Now with hstore transformations, role-aware snapshots, and a cleaner CLI. Built for Postgres devs doing CDC, replication, or analytics. Check it out → xata.io/blog/pgstrea... Open source & ready to use.

Can an AI agent handle your Postgres on-call? @divyendusingh.com from @xata.io is speaking at the Postgres Berlin Meetup tomorrow showing how we’re using LLMs to automate DB diagnostics, fixes, and even PRs. Come see “Xata Agent” in action. 📍 RSVP: www.meetup.com/postgresql-m...

What if your Postgres cluster could hibernate when idle and wake instantly when needed? At Xata, we built exactly that with a CNPG plugin. → Cut costs → Power ephemeral DBs → Open source Full details: xata.io/blog/making-...

Data exploration is easier with the ability to generate SQL from a simple question. No need to worry about syntax. Just dive into the data.

Branch metrics provide insight into CPU, memory, throughput, egress, and more. Use interactive charts to view trends over time or investigate anomalous spikes. Metrics are stored for up to 60 days at no additional cost.

Have a branch you don’t need running all the time? Save money by setting scale-to-zero as the default for a project or override it in the branch settings.

Our list of supported extensions is growing every day. Got any requests?

🚀 Congrats to @apatheticmagpie.bsky.social for being named Woman of the Month by Postgres Women India! 🎉 She shares her Postgres journey, open-source work on pgroll and pgstream and her role in co-organizing the Postgres on Kubernetes and Postgres & AI Summits. 👉 postgreswomen.in/gulcin-yildi...

Xata @ PGDay UK 2025 🐘 Andrew dove into pgroll, our OSS tool for zero-downtime Postgres schema migrations. Great Qs from the community: logical replication, multi-schema & more. Always grateful for the Postgres crowd in London!

You have full control over your branches directly from the console. Adjust the instance size, add replicas, tune compute settings, and modify your Postgres config.