diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-04-27 00:13:00 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-04-27 00:13:00 -0400 |
commit | aa0c797c901d43a5cd7ce74b0348198792c0646b (patch) | |
tree | 20e45660ee3b65560c9f40581085dcb6c02232fd /contrib/btree_gist/btree_gist.c | |
parent | 6b87144323fe4cf920ea4d095cce93a84c9b8922 (diff) | |
download | postgresql-aa0c797c901d43a5cd7ce74b0348198792c0646b.tar.gz postgresql-aa0c797c901d43a5cd7ce74b0348198792c0646b.zip |
Fix syslogger's rotation disable/re-enable logic.
If it fails to open a new log file, the syslogger assumes there's something
wrong with its parameters (such as log_directory), and stops attempting
automatic time-based or size-based log file rotations. Sending it SIGHUP
is supposed to start that up again. However, the original coding for that
was really bogus, involving clobbering a couple of GUC variables and hoping
that SIGHUP processing would restore them. Get rid of that technique in
favor of maintaining a separate flag showing we've turned rotation off.
Per report from Mark Kirkwood.
Also, the syslogger will automatically attempt to create the log_directory
directory if it doesn't exist, but that was only happening at startup.
For consistency and ease of use, it should do the same whenever the value
of log_directory is changed by SIGHUP.
Back-patch to all supported branches.
Diffstat (limited to 'contrib/btree_gist/btree_gist.c')
0 files changed, 0 insertions, 0 deletions