Alvaro Herrera <alvhe...@2ndquadrant.com> writes:
> Michael Paquier wrote:
>> So a worker does not see changes in postgresql.conf once it is run and
>> processes a database, no? The launcher does run ProcessConfigFile()
>> when SIGHUP shows up though.
> Maybe this is something that we should change.
Yeah, checking for SIGHUP in the worker outer loop (ie once per table)
seems like a reasonable thing.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
