Re: pgsql: postgres_fdw: Inherit the local transaction's access/deferrable
Etsuro Fujita <etsuro.fujita@gmail.com>
From: Etsuro Fujita <etsuro.fujita@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>,
Etsuro Fujita <efujita@postgresql.org>, pgsql-hackers@lists.postgresql.org
Date: 2026-03-05T00:04:51Z
Lists: pgsql-hackers
On Mon, Feb 16, 2026 at 10:15 AM Michael Paquier <michael@paquier.xyz> wrote: > On Sun, Feb 15, 2026 at 05:40:13PM +0900, Etsuro Fujita wrote: > > This patch 1) modifies postgres_fdw so that it opens remote > > transactions in read-only mode if the corresponding local transaction > > is read-only, as noted in the documentation, but 2) keeps the existing > > behavior of login triggers that they can write even if the invoking > > transaction is read-only. So declaring a transaction as read-only on > > the local side doesn't mean it blocks all write operations on the > > remote side; it still allows login triggers invoked on the remote side > > to write. Considering typical use-cases of such triggers, this seems > > reasonable to me. I think it might be a good idea to add a note about > > it to the documentation, though. > > > > I'd like to re-propose this patch for v19, as mentioned in this thread. > > Considering again that for v19 sounds like a sensible thing to do. > Before feature freeze, not after. :D Will do. Best regards, Etsuro Fujita
Commits
-
postgres_fdw: Inherit the local transaction's access/deferrable modes.
- de28140ded8d 19 (unreleased) landed
- e5a3c9d9b5ce 18.0 cited
-
Revert "postgres_fdw: Inherit the local transaction's access/deferrable modes."
- 7d4667c6203d 18.0 landed