• Sources: primary
  • Summary: The proxy keeps the transaction on the primary and sends eligible top-level SELECTs without locking clauses to a replica connection, which waits for a target LSN and, after the first write, imports the transaction's XIDs to see its own writes. A patched libpq adds a splittable marker and XID list to ReadyForQuery, repeatable read and serializable transactions are never split, and the borrowed replica is pinned until commit or rollback. The post contrasts this with Pgpool-II, PgBouncer, Vitess and Aurora's in-engine read consistency.
  • Why it matters: It shows the exact conditions under which mid-transaction replica reads stay correct on read committed, a gap stock PostgreSQL proxies leave on the primary.