Re: pgsql: postgres_fdw: Inherit the local transaction's access/deferrable

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Etsuro Fujita <efujita(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: postgres_fdw: Inherit the local transaction's access/deferrable
Date: 2026-02-16 01:15:08
Message-ID: aZJvnGgG95_Rs1Il@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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
--
Michael

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2026-02-16 03:19:23 pgsql: pgcrypto: Tweak error message for incorrect session key length
Previous Message Etsuro Fujita 2026-02-15 08:40:13 Re: pgsql: postgres_fdw: Inherit the local transaction's access/deferrable

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-02-16 01:49:14 Re: Having problems generating a code coverage report
Previous Message Michael Paquier 2026-02-16 01:10:58 Re: Fix uninitialized xl_running_xacts padding