Michael Paquier wrote: > On Mon, Mar 23, 2015 at 11:07 PM, Tom Lane <[email protected]> wrote: > > Alvaro Herrera <[email protected]> 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. > > That sounds fine to me as well. A patch would not be complicated, but > is this portion really 9.5 material?
IMO yes. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
