diff options
author | Etsuro Fujita <efujita@postgresql.org> | 2025-06-01 17:30:00 +0900 |
---|---|---|
committer | Etsuro Fujita <efujita@postgresql.org> | 2025-06-01 17:30:00 +0900 |
commit | e5a3c9d9b5ce535151d3a7e3173e8d27d2d8cd58 (patch) | |
tree | 3693798fef888b1241a158947636a811fcfa6c3b /src/bin/pg_dump/po/LINGUAS | |
parent | b006bcd5310eb2dad0828a286b79babce4953143 (diff) | |
download | postgresql-master.tar.gz postgresql-master.zip |
Previously, postgres_fdw always 1) opened a remote transaction in READ
WRITE mode even when the local transaction was READ ONLY, causing a READ
ONLY transaction using it that references a foreign table mapped to a
remote view executing a volatile function to write in the remote side,
and 2) opened the remote transaction in NOT DEFERRABLE mode even when
the local transaction was DEFERRABLE, causing a SERIALIZABLE READ ONLY
DEFERRABLE transaction using it to abort due to a serialization failure
in the remote side.
To avoid these, modify postgres_fdw to open a remote transaction in the
same access/deferrable modes as the local transaction. This commit also
modifies it to open a remote subtransaction in the same access mode as
the local subtransaction.
Although these issues exist since the introduction of postgres_fdw,
there have been no reports from the field. So it seems fine to just fix
them in master only.
Author: Etsuro Fujita <etsuro.fujita@gmail.com>
Reviewed-by: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/CAPmGK16n_hcUUWuOdmeUS%2Bw4Q6dZvTEDHb%3DOP%3D5JBzo-M3QmpQ%40mail.gmail.com
Diffstat (limited to 'src/bin/pg_dump/po/LINGUAS')
0 files changed, 0 insertions, 0 deletions