Re: Proper way to reload config files in backend SIGHUP handler

Поиск
Список
Период
Сортировка
От Euler Taveira
Тема Re: Proper way to reload config files in backend SIGHUP handler
Дата
Msg-id CAHE3wghpZuR96J0u=HKDLHfCzJr1TZGBWU0EzNbJyLRLe0=YHQ@mail.gmail.com
обсуждение исходный текст
Ответ на Proper way to reload config files in backend SIGHUP handler  (Mike Palmiotto <mike.palmiotto@crunchydata.com>)
Ответы Re: Proper way to reload config files in backend SIGHUP handler  (Mike Palmiotto <mike.palmiotto@crunchydata.com>)
Список pgsql-hackers
2018-05-03 19:25 GMT-03:00 Mike Palmiotto <mike.palmiotto@crunchydata.com>:
> I am writing a PostgreSQL extension and need to reload certain
> extension-managed files whenever the postmaster is reloaded/receives SIGHUP,
> but cannot find anything that looks like a standard way to do that. Is there a
> hook or recommended method or something else I am missing?
>
Signals are initially blocked in bgworker. You have to unblock them
(see BackgroundWorkerUnblockSignals) to allow your extension to
customize its signal handlers. See an example in worker_spi test
module.


-- 
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento


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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: unused_oids script is broken with bsd sed
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: ignore_system_indexes affects DROP SCHEMA ... CASCADE reportednumber of objects dropped