Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect
Date: 2025-11-27 05:17:15
Message-ID: CAHGQGwGxSVPia+ZtJxyqWTdP_-YG_YPb=CMrZpC7fTjknARX=A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 27, 2025 at 11:46 AM Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> On Thu, Nov 27, 2025 at 2:37 AM Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
> > Looking at v3 raises two questions for me.
> >
> > First is if we should have a doc notion of which variables ought to be
> > set to what.
>
> Are you suggesting that we document which GUC parameters should be set,
> and to what values, for logical replication? We already have a section on this
> in logical-replication.sgml. Is that sufficient?
>
>
> > Second, how do we actually test that subscription connection options
> > are applied on the subscriber side? Can we have TAP for this (is is
> > worth the troubles)?
>
> +1 on adding a test. One idea is to enable log_replication_commands via
> the CONNECTION option and then check that the publisher’s log contains
> the message "received replication command: IDENTIFY_SYSTEM".
> There may be a cleaner way to test this, though.

I've added the test and attached it as patch v4-0002.

The test enables log_disconnections via the CONNECTION string and then checks
that the publisher's log contains the expected disconnection message after
the logical replication connection is reestablished.

Regards,

--
Fujii Masao

Attachment Content-Type Size
v4-0001-PG15-PG16-Honor-GUC-settings-specified-in-CREATE-SUBSCRIPTI.txt text/plain 4.1 KB
v4-0001-Honor-GUC-settings-specified-in-CREATE-SUBSCRIPTI.patch application/octet-stream 3.9 KB
v4-0002-Add-TAP-test-for-GUC-settings-passed-via-CONNECTI.patch application/octet-stream 3.1 KB
v4-0001-PG17-Honor-GUC-settings-specified-in-CREATE-SUBSCRIPTI.txt text/plain 3.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-11-27 05:18:29 Re: Consistently use palloc_object() and palloc_array()
Previous Message shveta malik 2025-11-27 05:12:05 Re: How can end users know the cause of LR slot sync delays?