From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Frost <jeff(at)pgexperts(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #8225: logging options don't change after reload |
Date: | 2013-06-14 02:48:10 |
Message-ID: | 25869.1371178090@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Jeff Frost <jeff(at)pgexperts(dot)com> writes:
> What I don't understand is the new log file being created from the new
> log_filename setting but then nothing being logged into it. Is it the
> postmaster which creates that file? I would've thought it would be
> the logger process?
Hm, I hadn't focused on that --- that *is* pretty bizarre. The
postmaster creates the log file initially before forking the syslogger,
but subsequent rotations are handled by the syslogger process.
Is it possible that your systems are running on the hairy edge of ENFILE
limits? I notice that the syslogger will silently fail to rotate if it
gets ENFILE while trying to open the new log file. That doesn't look
like it'd explain the lack of log_checkpoint activity, though. Also,
usually people notice this state because everything else on the box
starts to fall over ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Frost | 2013-06-14 03:44:17 | Re: BUG #8225: logging options don't change after reload |
Previous Message | Jeff Frost | 2013-06-14 01:14:05 | Re: BUG #8225: logging options don't change after reload |