MIME-Version: 1.0
References: <E1uLe9X-000zsY-2g@gemulon.postgresql.org>
 <ed2296f1-1a6b-4932-b870-5bb18c2591ae@oss.nttdata.com>
 <aD0bg6Km5IigzUkC@paquier.xyz>
 <CAPmGK17Vf4fWt=+kCZ8V3JP7jO6iMrUze7TjOVtGzZwNbevnwg@mail.gmail.com>
 <b269f7ad-90a7-4217-a58e-038899148718@oss.nttdata.com>
 <CAPmGK14yYoO2iBg7SoT3WdnAKoCpWy_LPdoTDepJ21-Yf8TiKA@mail.gmail.com>
 <aZJvnGgG95_Rs1Il@paquier.xyz>
In-Reply-To: <aZJvnGgG95_Rs1Il@paquier.xyz>
From: Etsuro Fujita <etsuro.fujita@gmail.com>
Date: Thu, 5 Mar 2026 09:04:51 +0900
Message-ID: 
 <CAPmGK14uMcr522jWFWjjwO2-71J7x0OaJfroyqmO+bUnCd5dOw@mail.gmail.com>
Subject: Re: pgsql: postgres_fdw: Inherit the local transaction's
 access/deferrable
To: Michael Paquier <michael@paquier.xyz>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>,
 Etsuro Fujita <efujita@postgresql.org>,
	pgsql-hackers@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAPmGK14uMcr522jWFWjjwO2-71J7x0OaJfroyqmO%2BbUnCd5dOw%40mail.gmail.com>
Precedence: bulk

On Mon, Feb 16, 2026 at 10:15=E2=80=AFAM Michael Paquier <michael@paquier.x=
yz> 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