On Mon, Feb 16, 2026 at 10:15 AM Michael Paquier <[email protected]> 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
