Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect
| От | Amit Kapila |
|---|---|
| Тема | Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect |
| Дата | |
| Msg-id | CAA4eK1JBg=k_4_0BX3p4usPs-a8-7FbPuPW8B2Rf1eUs5i_WLg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect (Fujii Masao <masao.fujii@gmail.com>) |
| Список | pgsql-hackers |
On Tue, Dec 2, 2025 at 8:30 PM Fujii Masao <masao.fujii@gmail.com> wrote: > > On Tue, Dec 2, 2025 at 9:08 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > Is it possible that we append the predefined options to the options > > given by the user to avoid extra round-trip? > > One idea is to add a function, similar to libpqrcv_get_dbname_from_conninfo() > in libpqwalreceiver.c, that extracts the options string from the conninfo, > to append the required fixed settings, and then to use the combined string as > the value of the options parameter. > Yes, but libpqrcv_get_dbname_from_conninfo() is an exposed function, we can implement something internal for libpqwalreceiver.c like conninfo_add_defaults() present in fe-connect.c. > Do you think implementing this is worthwhile > to avoid the extra round trip? > I think so. Today, we have three variables, tomorrow there could be more such variables as well and apart from avoiding extra round trips, the idea to append options to provided options (if any) sounds more logical to me. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: