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 02:46:10
Message-ID: CAHGQGwHkH6YSje+KaoZ2TeKSFoHYDBGtKq43=UmPbjDn0pHwtA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message 邱宇航 2025-11-27 02:51:15 Re: Add pg_buffercache_mark_dirty[_all] functions to the pg_buffercache
Previous Message Mihail Nikalayeu 2025-11-27 02:30:00 Re: Patch: VACUUM should ignore (CREATE |RE)INDEX CONCURRENTLY for xmin horizon calculations