| From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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-03-05 00:04:51 |
| Message-ID: | CAPmGK14uMcr522jWFWjjwO2-71J7x0OaJfroyqmO+bUnCd5dOw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Feb 16, 2026 at 10:15 AM Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-03-05 00:26:38 | pgsql: Change default value of default_toast_compression to "lz4", take |
| Previous Message | Etsuro Fujita | 2026-03-05 00:00:55 | Re: pgsql: postgres_fdw: Inherit the local transaction's access/deferrable |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | yonghao_lee | 2026-03-05 00:40:10 | [PATCH] Fix improper tuple deallocation in import_pg_statist() |
| Previous Message | Chao Li | 2026-03-05 00:04:49 | Re: pg_resetwal.c: duplicate '0' in hex character set for -l option validation |