Re: Use standard SIGHUP and SIGTERM handlers in autoprewarm module

Поиск
Список
Период
Сортировка
От Bharath Rupireddy
Тема Re: Use standard SIGHUP and SIGTERM handlers in autoprewarm module
Дата
Msg-id CALj2ACUdvTiD3zpGMsO6HcMOLYDs=LXRkX72NUCExVdna=qP=Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Use standard SIGHUP and SIGTERM handlers in autoprewarm module  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Ответы Re: Use standard SIGHUP and SIGTERM handlers in autoprewarm module
Список pgsql-hackers
On Wed, Nov 4, 2020 at 2:36 PM Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
>
> Regarding other two patches, I think that it's better to use MyLatch
> rather than MyProc->procLatch or walrcv->latch in WaitLatch() and
> ResetLatch(), like other code does. Attached are the updated versions
> of the patches. Thought?
>

+1 for replacing MyProc->procLatch with MyLatch in the autoprewarm
module, and the patch looks good to me.

I'm not quite sure to replace all the places in the walreceiver
process, for instance in WalRcvForceReply() we are using spinlock to
acquire the latch pointer and . Others may have better thoughts on
this.

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com



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

Предыдущее
От: Stephen Frost
Дата:
Сообщение: Re: automatic analyze: readahead - add "IO read time" log message
Следующее
От: Tom Lane
Дата:
Сообщение: Re: "unix_socket_directories" should be GUC_LIST_INPUT?