Horton

Re: Options to control remote transactions’ access/deferrable modes in postgres_fdw

Etsuro Fujita <etsuro.fujita@gmail.com>

View thread View on postgr.es
From: Etsuro Fujita <etsuro.fujita@gmail.com>
To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-03-04T23:52:22Z
Lists: pgsql-hackers

Attachments

On Wed, Feb 25, 2026 at 7:22 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> This was reverted in commit 7d4667c62.  I'd like to re-propose it for
> v19, as mentioned in [1].  Attached is a new patch, in which I added
> to the documentation a note about login triggers executed on the
> remote side, as discussed in [1].  Other than that, no changes.  I've
> added this to the upcoming CF.

Here is an updated version of the patch.  Changes are:

* On second thought, I think the name of the variable
top_read_only_level added to connection.c by the patch is a bit long,
so I renamed it to top_read_only.  Does that make sense?  Other than
that, no code changes.
* I also added/modified some comments.

Comments welcome!

Best regards,
Etsuro Fujita

Commits

  1. postgres_fdw: Inherit the local transaction's access/deferrable modes.

  2. Revert "postgres_fdw: Inherit the local transaction's access/deferrable modes."