Xata 🦋 @xata

Postgres at scale — with copy-on-write branching, data masking, separated storage & compute , 100% Postgres and your own cloud xata.io 🌏 Earth Joined November 2020

Tweets

1K
Followers

4K
Following

417
Likes

1K

Xata 🦋 @xata

2 days ago

Once the new store had a real retention window, we deleted the vendor client, the routing, the override header, the flag, the config. Full write-up: xata.io/blog/how-we-re…

0 0 0 92 0

View Details

Best part of the cutover: both backends in code, behind a flag, with a header to flip backends per request. Same chart on both, side by side, for a week. That's how we caught a double-count where pod aggregates were summing with the per-container series.

1 0 0 98 0

View Details

Xata 🦋 @xata

2 days ago

We rebuilt the metrics view for every Postgres branch on @xata. Out of a central observability vendor, into a per-cell @VictoriaMetrics stack. Six weeks of work, no user-visible downtime in the console. Here's what we learned. 🧵

1 2 7 798 3

View Details

Xata 🦋 @xata

a week ago

Repo: github.com/xataio/nextjs-…

0 0 0 241 0

View Details

Xata 🦋 @xata

a week ago

We open-sourced a Next.js + Postgres starter with 6 Claude Code skills. Each skill wraps the Xata CLI for one workflow: branch, migrate, complete, rollback, clone-with-anonymization, setup. Tutorial: xata.io/blog/building-…

1 2 9 505 4

View Details

Xata 🦋 @xata

2 weeks ago

@monicasarbu and the Xata team are at AWS Summit Hamburg today, in the AWS Startup Zone, Hall 4. If you're thinking about Postgres for agent scale, come find us.

0 1 2 138 0

View Details

Xata 🦋 @xata

2 weeks ago

DeltaX is a Postgres extension that adds columnar storage and time-series compression. Data lives in regular Postgres tables. pg_dump, replication, and crash recovery all keep working without change. Under the hood: → Type-specific codecs (Gorilla XOR, delta-of-delta, dictionary, block-LZ4) → Vectorized Rust execution, bypasses per-row ExecQual → Segment pruning with bloom filters → Parallel aggregation → Shared-memory blob cache Status is alpha, PostgreSQL 17 and 18. Star the project: github.com/xataio/deltax

1 1 2 1K 1

View Details

Xata 🦋 @xata

2 weeks ago

DeltaX is now public: the TimescaleDB alternative with Apache 2.0. Preliminary ClickBench: ~4.7× faster on analytical queries.

2 2 24 1.2M 7

View Details

Xata 🦋 @xata

2 weeks ago

Built quietly over the past months. Star the repo and run the benchmark: github.com/xataio/deltax

Tudor Golubenco @tudor_g

2 weeks ago

There’s something I’ve been feverishly working on, and I just turned the repo public: pg_deltax (δx) - Fast time-series extension for PostgreSQL. Basically an Apache-licensed Timescale alternative. GitHub link in the thread.

7 7 76 12K 24

0 1 2 351 0

View Details

Xata 🦋 @xata

3 weeks ago

The decode-time table filter is a community contribution from @blakewatters add_tables and filter_tables go straight through to wal2json. Thanks Blake. Release: github.com/xataio/pgstrea…

0 0 0 112 0

View Details

Xata 🦋 @xata

3 weeks ago

pgstream v1.0.2 is out. Post-snapshot catch-up no longer stalls on bulk INSERT or DELETE tables (Postgres sink coalesces flushes now). You can also filter tables at decode time inside the source Postgres via wal2json. Plus Go 1.26.3 security fixes; v0.9.12 backports that one too.

1 3 4 895 3

View Details

Xata 🦋 @xata

4 weeks ago

Every Xata Postgres branch now ships with a managed PgBouncer endpoint, included. A Postgres connection costs about 5MB of backend memory. Fine when traffic comes from a handful of app servers. Breaks when traffic comes from serverless functions, edge workers, or AI agents that open a connection per request. Postgres wants fewer, long-lived connections. Modern apps produce many short-lived ones. A pooler reconciles that. We chose to ship one PgBouncer pod per branch, on the same node as the database, in the same memory budget. Pool size auto-tunes to 0.9 of max_connections and re-tunes when the instance changes. If you connect directly to Postgres, append -pooler to your branch ID: > postgresql[:]//user:pass@branch-id-pooler[.]us-east-1[.]xata[.]sh:5432/postgres One-line change in your connection string. Branching gives you cheap copies of Postgres. Pooling gives those copies somewhere to take traffic. We needed both. xata.io/blog/a-connect…

0 4 5 1K 0

View Details

Tudor Golubenco @tudor_g

a month ago

We needed a storage layer that can scale to a huge number of volumes (think millions) for our Postgres platform. Most of the existing storage systems are optimized for a few volumes with really high performance. But we needed the opposite: a very large number of mostly idle volumes. So we wrote our own. It’s called Xatastor and it enables Postgres-per-tenant use cases, “ephemeral” dbs for agents, free tiers, etc. Supports copy-on-write snapshots, clones, and thin provisioning. It’s based on ZFS and NVMe-oF as key technologies. Link with all the details in the first reply.

2 13 30 8K 14

View Details

Xata 🦋 @xata

a month ago

We rebuilt the storage engine behind Xata Cloud. And we're talking about why. Architecture deep-dive by @tudor_g xata.io/blog/xatastor-…

3 10 78 1.2M 19

View Details

Monica 🦋 @monicasarbu

a month ago

We’re seeing this firsthand with AI platforms we partner with: 👉 every agent needs its own isolated Postgres DB 👉 at scale, that’s millions of databases 👉 many on free tiers → cost matters a lot That combination breaks traditional storage. Most systems are built for a few always-on volumes. Agents need the opposite: millions of mostly idle ones. So we built Xatastor. It enables Postgres-per-tenant use cases, ephemeral DBs for agents, free tiers, and supports copy-on-write snapshots, clones, and thin provisioning.

1 5 14 1K 3

View Details

Xata 🦋 @xata

a month ago

Richard on what changed and what didn't: xata.io/blog/ai-codes-…

0 0 1 116 1

View Details

Xata 🦋 @xata

a month ago

AI codes. Humans engineer. AI is already good at boilerplate, search, command line, simple fixes with feedback loops. Outsource it. Engineers still own decisions, distillation, organizational context, code review, and breaking out of incorrect assumptions.