Re: Binary support for pgoutput plugin
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Dave Cramer <davecramer@gmail.com>, Daniel Gustafsson <daniel@yesql.se>,
Petr Jelinek <petr@2ndquadrant.com>,
Alvaro Herrera <alvherre@2ndquadrant.com>,
Michael Paquier <michael@paquier.xyz>,
Dmitry Dolgov <9erthalion6@gmail.com>,
Thomas Munro <thomas.munro@gmail.com>,
Tomas Vondra <tomas.vondra@2ndquadrant.com>,
Petr Jelinek <petr.jelinek@2ndquadrant.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-07-14T23:46:52Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > There's also send/receive functions that do not work across systems, > unfortunately :(. In particular record and array send functions embed > type oids and their receive functions verify that they match the local > system. Which basically means that if there's any difference in oid > assignment order between two systems that they will not allow to > send/recv such data between them :(. It's not a problem particularly for built-in types, but I agree there's an issue for extension types. > I've several times suggested that we should remove those type checks in > recv, as they afaict don't provide any actual value. But unfortunately > there hasn't been much response to that. See e.g. > https://postgr.es/m/20160426001713.hbqdiwvf4mkzkg55%40alap3.anarazel.de Maybe we could compromise by omitting the check if both OIDs are outside the built-in range? regards, tom lane
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