Re: Table-level log_autovacuum_min_duration
От | Alvaro Herrera |
---|---|
Тема | Re: Table-level log_autovacuum_min_duration |
Дата | |
Msg-id | 20150324024620.GJ3636@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Table-level log_autovacuum_min_duration (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: Table-level log_autovacuum_min_duration
|
Список | pgsql-hackers |
Michael Paquier wrote: > On Mon, Mar 23, 2015 at 11:07 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Alvaro Herrera <alvherre@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. > > 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
В списке pgsql-hackers по дате отправления: