Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect
| От | Fujii Masao |
|---|---|
| Тема | Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect |
| Дата | |
| Msg-id | CAHGQGwHkH6YSje+KaoZ2TeKSFoHYDBGtKq43=UmPbjDn0pHwtA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect (Kirill Reshke <reshkekirill@gmail.com>) |
| Ответы |
Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect
|
| Список | pgsql-hackers |
On Thu, Nov 27, 2025 at 2:37 AM Kirill Reshke <reshkekirill@gmail.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
В списке pgsql-hackers по дате отправления: