| From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
|---|---|
| To: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: postgres_fdw: transaction mode inheritance corner cases |
| Date: | 2026-10-01 17:37:29 |
| Message-ID: | CAPmGK173Jw9SAgb8QvmKPVMF5ORqf2x8mM0iXG7wS0yHfbbqsQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 2, 2026 at 2:30 AM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
> On Thu, Oct 1, 2026 at 3:27 AM Matheus Alcantara
> <matheusssilv97(at)gmail(dot)com> wrote:
> > 1: read-write local transactions can no longer query a hot standby
>
> Ah, I think this is too restrictive, so I changed my mind; I'd like to
> propose to keep the current behavior and instead modify the
> documentation like this:
Sorry I forgot this example:
Local READ ONLY transactions propagate their read-only mode to remote
sessions. (This is also applied to subtransactions.) Note that this
does not prevent login triggers executed on remote servers from
writing.
Also, local DEFERRABLE transactions propagate their deferrable mode to
remote sessions. (This is only applied to remote servers 9.1 and
newer.)
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Etsuro Fujita | 2026-10-01 17:32:44 | Re: postgres_fdw: transaction mode inheritance corner cases |