Re: Table-level log_autovacuum_min_duration - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Table-level log_autovacuum_min_duration
Date
Msg-id 31249.1427119632@sss.pgh.pa.us
Whole thread Raw
In response to Re: Table-level log_autovacuum_min_duration  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Table-level log_autovacuum_min_duration
Re: Table-level log_autovacuum_min_duration
List pgsql-hackers
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.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Вадим Горбачев
Date:
Subject: proposal GSoC 2015 task: Allow access to the database via HTTP
Next
From: Tom Lane
Date:
Subject: Re: Order of enforcement of CHECK constraints?