Re: Move walreceiver state assignment (to WALRCV_STREAMING) in WalReceiverMain()

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Move walreceiver state assignment (to WALRCV_STREAMING) in WalReceiverMain()
Дата
Msg-id ZXnAuwAP0ZD_96QS@paquier.xyz
обсуждение исходный текст
Ответ на Re: Move walreceiver state assignment (to WALRCV_STREAMING) in WalReceiverMain()  ("Euler Taveira" <euler@eulerto.com>)
Ответы Re: Move walreceiver state assignment (to WALRCV_STREAMING) in WalReceiverMain()  ("Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>)
Список pgsql-hackers
On Tue, Dec 12, 2023 at 04:54:32PM -0300, Euler Taveira wrote:
> Couldn't it give up before starting if you apply your patch? My main concern is
> due to a slow system, the walrcv_connect() took to long in WalReceiverMain()
> and the code above kills the walreceiver while in the process to start it.
> Since you cannot control the hardcoded WALRCV_STARTUP_TIMEOUT value, you might
> have issues during overload periods.

Sounds like a fair point to me, this area is trickier than it looks.
Another thing that I'm a bit surprised with is why it would be OK to
switch the status to STREAMING only we first_stream is set, discarding
the restart case.
--
Michael

Вложения

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Remove MSVC scripts from the tree
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Subsequent request from pg client