pgsql: Set the correct context (PGC_SIGHUP) for log_autovacuum, per

Started by Tom Lanealmost 19 years ago3 messagescomitters
Jump to latest
#1Tom Lane
tgl@sss.pgh.pa.us

Log Message:
-----------
Set the correct context (PGC_SIGHUP) for log_autovacuum, per ITAGAKI Takahiro.
Fix grammatical errors in its description.

Modified Files:
--------------
pgsql/doc/src/sgml:
config.sgml (r1.142 -> r1.143)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml?r1=1.142&r2=1.143)
pgsql/src/backend/utils/misc:
guc.c (r1.417 -> r1.418)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c?r1=1.417&r2=1.418)

#2Bruce Momjian
bruce@momjian.us
In reply to: Tom Lane (#1)
Re: pgsql: Set the correct context (PGC_SIGHUP) for log_autovacuum, per

"Tom Lane" <tgl@postgresql.org> writes:

Log Message:
-----------
Set the correct context (PGC_SIGHUP) for log_autovacuum, per ITAGAKI Takahiro.

Didn't we say we were going to change this to log_autovacuum_min_duration?
Having a GUC called log_autovacuum for which 0 means "on" and 1 means "on
sometimes" is surprising.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

#3ITAGAKI Takahiro
itagaki.takahiro@oss.ntt.co.jp
In reply to: Bruce Momjian (#2)
Re: pgsql: Set the correct context (PGC_SIGHUP) for log_autovacuum, per

Gregory Stark <stark@enterprisedb.com> wrote:

Didn't we say we were going to change this to log_autovacuum_min_duration?
Having a GUC called log_autovacuum for which 0 means "on" and 1 means "on
sometimes" is surprising.

Hmm, how about "log_min_duration_autovacuum" ?
We have log_min_duration_statement, that behaves in the same manner.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center