Re: Making WAL receiver startup rely on GUC context for primary_conninfo and primary_slot_name

Поиск
Список
Период
Сортировка
От Sergei Kornilov
Тема Re: Making WAL receiver startup rely on GUC context for primary_conninfo and primary_slot_name
Дата
Msg-id 67523061547115016@iva5-d3020dc3459d.qloud-c.yandex.net
обсуждение исходный текст
Ответ на Re: Making WAL receiver startup rely on GUC context forprimary_conninfo and primary_slot_name  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Making WAL receiver startup rely on GUC context forprimary_conninfo and primary_slot_name  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
Дерево обсуждения 
Hello

> I was just double-checking the code, and it is possible to remove the
> part from RequestXLogStreaming() which sets slotname and conninfo to
> '\0', so I removed that part from my local branch to simplify the
> code.

Without both ready_to_display and cleaning in RequestXLogStreaming we do not show outdated PrimaryConnInfo in case
walreceiverjust started, but does not connected yet? While waiting walrcv_connect for example.
 

regards, Sergei

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Dean Rasheed
Дата:
Сообщение: Policy on cross-posting to multiple lists
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: [Sender Address Forgery]Re: error message when subscriptiontarget is a partitioned table