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

From: Euler Taveira <euler(at)timbira(dot)com(dot)br>
To: Mike Palmiotto <mike(dot)palmiotto(at)crunchydata(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proper way to reload config files in backend SIGHUP handler
Date: 2018-05-04 00:43:37
Message-ID: CAHE3wghpZuR96J0u=HKDLHfCzJr1TZGBWU0EzNbJyLRLe0=YHQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2018-05-03 19:25 GMT-03:00 Mike Palmiotto <mike(dot)palmiotto(at)crunchydata(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-05-04 02:26:01 Re: ignore_system_indexes affects DROP SCHEMA ... CASCADE reported number of objects dropped
Previous Message Peter Eisentraut 2018-05-04 00:20:18 Re: unused_oids script is broken with bsd sed