diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-04-27 00:12:47 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-04-27 00:12:47 -0400 |
commit | 1869f000b0a31d71906ad6ac6e86b08a65f723f0 (patch) | |
tree | 7c98f37dc5db24ae14611bb65f8a72f2b34ff1d4 /src/backend/access/gist/gist.c | |
parent | 4fa520f147992616a08e5dbb34620dc46d664fc2 (diff) | |
download | postgresql-1869f000b0a31d71906ad6ac6e86b08a65f723f0.tar.gz postgresql-1869f000b0a31d71906ad6ac6e86b08a65f723f0.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 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions