public inbox for [email protected]
help / color / mirror / Atom feedFrom: Chao Li <[email protected]>
To: Fujii Masao <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect
Date: Mon, 24 Nov 2025 11:51:58 +0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAHGQGwEeJ6ijS=d5byU0Pq1J9YYGw+X=fyomd_d71sx5NOHdsA@mail.gmail.com>
References: <CAHGQGwGYV+-abbKwdrM2UHUe-JYOFWmsrs6=QicyJO-j+-Widw@mail.gmail.com>
<[email protected]>
<CAHGQGwGYG09DZnx7VVFvr7EfpC12sf+36D6iCSSAFMj66RY2_Q@mail.gmail.com>
<[email protected]>
<CAHGQGwGnkM8aYtxYAHXRPWYe90fbypz5TMezHDiy0Jt8=+BPpQ@mail.gmail.com>
<[email protected]>
<CAHGQGwEeJ6ijS=d5byU0Pq1J9YYGw+X=fyomd_d71sx5NOHdsA@mail.gmail.com>
> On Nov 22, 2025, at 22:14, Fujii Masao <[email protected]> wrote:
>
> On Sat, Nov 22, 2025 at 10:31 AM Chao Li <[email protected]> wrote:
>>
>>
>>
>>> On Nov 22, 2025, at 00:14, Fujii Masao <[email protected]> wrote:
>>>
>>> On Fri, Nov 21, 2025 at 6:24 PM Chao Li <[email protected]> wrote:
>>>> No, what I was thinking is that, we could combine the three set statement into one, like:
>>>>
>>>> ```
>>>> Set a = 1; set b = 2; set c = 3;
>>>> ```
>>>> So that sends a single statement to publisher server, that reduces round-trip from 3 times to one time.
>>>
>>> I see the point about combining the three SET commands to reduce round trips,
>>> but I think the current approach in the patch (i.e., issuing a separate
>>> SET command for each parameter) is sufficient. I still don't think
>>> the additional round trip during replication connection startup is
>>> a real concern. This approach is also consistent with what postgres_fdw
>>> and pg_dump already do.
>>>
>>
>> No problem. I don’t have a strong option here. I just saw you mentioned overhead of round trip and thought to improve. But I agree that overhead is tiny, not a real concern.
>
> Okay, thanks!
>
> I've updated the patch to use lengthof() as you suggested.
> The revised version is attached.
>
> Regards,
>
> --
> Fujii Masao
> <v3-0001-Honor-GUC-settings-specified-in-CREATE-SUBSCRIPTI.patch>
V3 looks good to me.
>> now all user specified options expect the 3 will be kept, will that expose a hold where user badly specifies some option that may break logical replication? If that’s true, then we need to parse user specified options and do some verifications.
>>
>
> Yeah, I agree that if certain GUCs can break logical replication,
> we should enforce "safe" values, just as we currently do for datestyle.
> And if any other GUCs can cause the issue, they could affect
> postgres_fdw etc, so the fix would need to be broader.
Just want to clarify if you mean you will handle this in a future patch?
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
view thread (37+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox