Edition of Wednesday 11 November 2026

Postgres logical replication beyond one writer

Comments on “Postgres logical replication beyond one writer”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Dimitri Fontaine builds a five-region, multi-writer Postgres system, the kind BDR targeted in 2014, from Postgres 19 RC1 logical replication and pg_auto_failover. In his tests, killing primaries under load lost no acknowledged rows when synchronized_standby_slots was set correctly, though a killed primary blocked its writer for about 51 seconds. Core still lacks DDL replication, conflict resolution and multi-writer ids, so he avoids conflicts through region-keyed rows and handles schema changes with a short write pause. The results come from his own lab runs.

Read the original at tapoueh.org. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 11 of 143 with a score of 0.70. The panel rated it highest on technical depth (0.98) and substantiated (0.92), lowest on audience breadth (0.50). Placed No. 11, No. 17 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed, heavily tested engineering writeup on Postgres 19 logical replication across regions with failover slots, row filters, and schema-change workarounds; substantive evidence and practical lessons for database builders.
AI judgeJudge 3gpt-5.6-luna
A deeply technical, experimentally backed engineering write-up showing practical limits and patterns for multi-region PostgreSQL logical replication, including failover, schema changes, conflicts, and region expansion.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.70total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.60
  • Reader interest0.78
  • Audience breadth0.50
  • Practical relevance0.79
  • Substantiated0.92
  • Technical depth0.98
  • New information0.84
  • Counts against: Promotional0.03
  • Counts against: Overclaim0.15

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.560.450.800.600.35+0.24+0.145
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.720.700.930.780.23+0.26+0.204
Audience breadthHow many people who build technology does it concern?0.430.500.560.500.13+0.13+0.065
Practical relevanceHow useful is it to someone who builds software or tech products?0.810.700.860.790.16+0.22+0.173
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.950.850.970.920.12+0.05+0.046
Technical depthHow technically substantive is it?1.000.950.990.980.05+0.05+0.049
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.850.700.980.840.28+0.05+0.042
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.040.050.010.030.04−0.19−0.006
OverclaimDo the headline or conclusions claim more than the body supports?0.180.200.060.150.14−0.11−0.016
Sum of contributions+0.702
Claim-check penalty0.000
Total, as published0.702

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #11 on Rubric, 11 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-11/11/"><img src="https://rubric.hrih.si/badge/2026-11-11/11.svg" alt="Ranked #11 on Rubric, 11 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 2 matches source · 4 no source given · 2 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenVersion

    Postgres 17 added failover = true for replication slots and the synchronized_standby_slots setting, so a logical walsender on a failover slot won't send WAL past what the listed standbys have flushed.

    The article gives no link or citation for it.

    The article says

    “Postgres 17 added failover = true for a replication slot, and the synchronized_standby_slots setting”

    The source says

    No source to compare with.

  2. Matches sourceGeneralization

    Patroni keeps its own permanent logical slots, which it creates on the leader and copies to the standbys, advancing their positions periodically.

    The cited source says the same thing.

    The article says

    “Patroni keeps its own permanent logical slots, which it creates on the leader and copies to the standbys, advancing their positions periodically”

    The source says

    “Patroni has its own concept of permanent replication slots . You declare a slot in the cluster configurationand Patroni makes sure it exists on every eligible node, copying the slot…”

    Source cited by the article: dbi-services.com/blog/surviving-a-patroni-failover-with-logical-replication

  3. Matches sourceVersion

    PgBouncer has proxied replication connections since version 1.23.0, listing them as logical or physical in SHOW CLIENTS and SHOW SERVERS.

    The cited source says the same thing.

    The article says

    “PgBouncer has proxied replication connections since version 1.23.0, and lists them as logical or physical in SHOW CLIENTS and SHOW SERVERS”

    The source says

    “Add support for replication connections through PgBouncer. ( #876”

    Source cited by the article: pgbouncer.org/changelog.html

  4. No source givenNumber

    In the authors' test, a killed primary blocked the writer for 51 to 52 seconds, with no holes and no rows ahead when synchronized_standby_slots was set correctly.

    The article gives no link or citation for it.

    The article says

    “primary killed 2 to 4 0 0 51 to 52 s”

    The source says

    No source to compare with.

  5. No source givenNumber

    In the authors' test of adding a fifth region with writers running, the first copy of 600,000 rows took 2 seconds, and all five regions ended with every acknowledged row and no apply or sync error.

    The article gives no link or citation for it.

    The article says

    “the first copy of 600,000 rows takes 2 seconds, and the source slot never kept more than 1 MB of WAL”

    The source says

    No source to compare with.

  6. Couldn’t checkVersion

    The Sequence Access Methods patch set (commitfest #4677) was returned with feedback for Postgres 19 and so is not included.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “The Sequence Access Methods patch set (commitfest #4677) was returned with feedback for Postgres 19, so it’s not in”

    The source says

    No passage could be compared.

    Source cited by the article: commitfest.postgresql.org/52/4677

  7. Couldn’t checkDate

    BDR 1.0 has its last commit on the 1.0 branch in November 2019.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “BDR 1.0, a patched 9.4 and a plugin, has its last commit on the 1.0 branch in November 2019”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/2ndQuadrant/bdr/tree/bdr-plugin/REL1_0_STABLE/doc

  8. No source givenGeneralization

    Core Postgres still does not replicate DDL, resolve conflicts, or hand out unique ids to several writers; these gaps are avoided by construction in the authors' design.

    The article gives no link or citation for it.

    The article says

    “It still doesn’t replicate DDL, so schema changes are a short pause, or pglogical or pgcopydb when a pause isn’t an option”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 1 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 11 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Postgres logical replication beyond one writer”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.