diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-07-21 15:19:46 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-07-21 15:19:46 -0400 |
commit | 670c0a1d474bf296dbcc1d6de912d4841f2ed643 (patch) | |
tree | e4a97a14031448cbf3be40914b6708db161a329c /src/backend/replication/logical/proto.c | |
parent | 606c3845988ddd9497cbbbf6fc559b91c76ed65d (diff) | |
download | postgresql-670c0a1d474bf296dbcc1d6de912d4841f2ed643.tar.gz postgresql-670c0a1d474bf296dbcc1d6de912d4841f2ed643.zip |
Weaken type-OID-matching checks in array_recv and record_recv.
Rather than always insisting on an exact match of the type OID in the
data to the element type or column type we expect, complain only when
both OIDs fall within the manually-assigned range. This acknowledges
the reality that user-defined types don't have stable OIDs, while
still preserving some of the mistake-detection value of the old test.
(It's not entirely clear whether to error if one OID is manually
assigned and the other isn't. But perhaps that case could arise in
cross-version cases where a former extension type has been imported
into core, so I let it pass.)
This change allows us to remove the prohibition on binary transfer
of user-defined arrays and composites in the recently-landed support
for binary logical replication (commit 9de77b545). We can just
unconditionally drop that check, since if the client has asked for
binary transfer it must be >= v14 and must have this change.
Discussion: https://postgr.es/m/CADK3HH+R3xMn=8t3Ct+uD+qJ1KD=Hbif5NFMJ+d5DkoCzp6Vgw@mail.gmail.com
Diffstat (limited to 'src/backend/replication/logical/proto.c')
-rw-r--r-- | src/backend/replication/logical/proto.c | 17 |
1 files changed, 2 insertions, 15 deletions
diff --git a/src/backend/replication/logical/proto.c b/src/backend/replication/logical/proto.c index 04b4f494bb9..9ff8097bf5f 100644 --- a/src/backend/replication/logical/proto.c +++ b/src/backend/replication/logical/proto.c @@ -494,22 +494,9 @@ logicalrep_write_tuple(StringInfo out, Relation rel, HeapTuple tuple, bool binar typclass = (Form_pg_type) GETSTRUCT(typtup); /* - * Choose whether to send in binary. Obviously, the option must be - * requested and the type must have a send function. Also, if the - * type is not built-in then it must not be a composite or array type. - * Such types contain type OIDs, which will likely not match at the - * receiver if it's not a built-in type. - * - * XXX this could be relaxed if we changed record_recv and array_recv - * to be less picky. - * - * XXX this fails to apply the restriction to domains over such types. + * Send in binary if requested and type has suitable send function. */ - if (binary && - OidIsValid(typclass->typsend) && - (att->atttypid < FirstGenbkiObjectId || - (typclass->typtype != TYPTYPE_COMPOSITE && - typclass->typelem == InvalidOid))) + if (binary && OidIsValid(typclass->typsend)) { bytea *outputbytes; int len; |