Re: Binary support for pgoutput plugin
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Chapman Flack <chap@anastigmatix.net>
Cc: Dave Cramer <davecramer@gmail.com>, Petr Jelinek <petr.jelinek@2ndquadrant.com>, David Fetter <david@fetter.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-06-08T01:18:41Z
Lists: pgsql-hackers
Hi, On 2019-06-07 21:16:12 -0400, Chapman Flack wrote: > On 06/07/19 21:01, Andres Freund wrote: > > On 2019-06-07 20:52:38 -0400, Chapman Flack wrote: > > That'd be a *lot* of additional complexity, and pretty much prohibitive > > from a performance POV. We'd have to not continue decoding on the server > > side *all* the time to give the client a chance to inquire additional > > information. > > Does anything travel in the client->server direction during replication? > I thought I saw CopyBoth mentioned. Is there a select()/poll() being done > so those messages can be received? Yes, acknowledgements of how far data has been received (and how far processed), which is then used to release resources (WAL, xid horizon) and allow synchronous replication to block until something has been received. - Andres
Commits
-
Weaken type-OID-matching checks in array_recv and record_recv.
- 670c0a1d474b 14.0 landed
-
Fix construction of updated-columns bitmap in logical replication.
- e8de627a3e05 11.9 landed
- d5daae47db5e 14.0 landed
- 71e561bd4bc2 12.4 landed
- 39d6aec1927c 10.14 landed
- 2f1f189cf880 13.0 landed
-
Allow logical replication to transfer data in binary format.
- 9de77b545313 14.0 landed
-
Phase 2 pgindent run for v12.
- 8255c7a5eeba 12.0 cited