Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect
| От | Chao Li |
|---|---|
| Тема | Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect |
| Дата | |
| Msg-id | 6E35E0EF-A842-408A-A264-DB6D428C2BD6@gmail.com обсуждение исходный текст |
| Ответ на | Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect (Fujii Masao <masao.fujii@gmail.com>) |
| Ответы |
Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect
|
| Список | pgsql-hackers |
> On Nov 21, 2025, at 15:47, Fujii Masao <masao.fujii@gmail.com> wrote: > >> >> 4. The commit message: >> ``` >> This commit removes the restriction by changing how logical replication >> connections are established so that GUC settings in the CONNECTION string >> are properly passed through to and uesd by the walsender. This enables >> ``` >> >> This is a little bit inaccurate, all user specified settings expected the 3 ones being overwritten will be honored. > > Are you suggesting that, because datestyle and the other two parameters > specified in CONNECTION aren(t actually applied by the walsender, > the commit message should explicitly mention that not all parameters > from CONNECTION are used? 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. Best regards, -- Chao Li (Evan) HighGo Software Co., Ltd. https://www.highgo.com/
В списке pgsql-hackers по дате отправления: