From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Lowry <dlowry@bju.edu>
Cc: Joshua D.Drake <jd@commandprompt.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: way to turn off epochs in log_filename
Date: Sat, 27 Oct 2007 11:30:29 -0400
Message-ID: <29409.1193499029@sss.pgh.pa.us> (raw)
In-Reply-To: <0072EC59-9FE8-461D-AD30-5116F19A1BF7@bju.edu>
References: <E11307EB-94DF-4CDD-A89D-0C88A84F2B99@bju.edu>
<26960.1193434395@sss.pgh.pa.us>
<20071026144005.3aa6cc29@scratch>
<27413.1193435100@sss.pgh.pa.us>
<20071026154202.501e9b75@scratch>
<0072EC59-9FE8-461D-AD30-5116F19A1BF7@bju.edu>
David Lowry <dlowry@bju.edu> writes:
> 1. Logrotate moves the old log file to a new name, equivalent to
> something like this:
> mv postgresql.log postgresql.log.1
> In the mean time, PG keeps writing to the same file.
> 2. Logrotate sends a HUP (as configured in the logrotate conf) to the
> postmaster process, which causes PG to close the old log file
> (postgresql.log.1) and open a new one (postgresql.log).
> If I understand correctly, you're saying that this process either
> won't work or isn't portable. Is that correct?
Specifically, PG does not respond to SIGHUP in the way you are imagining
above. The log-file-switch capability is either nonexistent (if no log
collector process) or built in (if log collector is active) and there
doesn't seem any value in driving the latter from outside PG.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, dlowry@bju.edu, jd@commandprompt.com
Subject: Re: way to turn off epochs in log_filename
In-Reply-To: <29409.1193499029@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox