Rebuilding Postgres Metrics on Self-Hosted VictoriaMetrics with Zero Downtime
Xata successfully migrated its PostgreSQL metrics to a self-hosted VictoriaMetrics stack over six weeks without any downtime for users. The transition was driven by the need for improved performance, scalability, and cost-effectiveness in their observability infrastructure. The new setup allows for metrics to be processed locally within each cell, enhancing efficiency and reducing reliance on external vendors.
- ▪Xata's PostgreSQL metrics were previously managed through a third-party observability vendor.
- ▪The migration to VictoriaMetrics was completed without any visible downtime for customers.
- ▪The new architecture allows for metrics to be processed locally within each cell, improving performance and reducing costs.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Xata |
| Canonical URL | https://xata.io/blog/how-we-rebuilt-postgresql-branch-metrics-on-victoriametrics-per-cell |
| Publication time | Wed, 03 Jun 2026 16:40:05 +0000 |
| Retrieval time | 2026-06-03T16:52:50.488Z |
| Last seen | 2026-06-03T16:52:50.488Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 9vAc6YVnLSg4 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Back to BlogHow we rebuilt PostgreSQL branch metrics on VictoriaMetrics, per cellHow we rebuilt Xata's PostgreSQL branch metrics on a self-hosted VictoriaMetrics stack in six weeks, with zero user-visible downtime.By:Alexis RicoPublished:Jun 2, 2026Reading time:6 min readBack to BlogTable of contents01. The starting picture02. Why we moved03. Why VictoriaMetrics04. The new shape05. The cutover06. What stuck with us07. What's nextTagsXataFeaturedDatabase branching in the age of AIInside Xatastor: ZFS + NVMe-oF for Postgres databasesIntroducing Xata OSS: Postgres platform with branchingEvery Xata branch is backed by real PostgreSQL. In the web console, each branch has a metrics view: CPU, memory, connections, disk I/O, network, WAL sync time, replication lag, database size.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Xata.
Discussion
0 commentsMore from Xata
