Re: A single escape required for log_filename - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: A single escape required for log_filename
Date
Msg-id 20090113221843.GH4656@tamriel.snowman.net
Whole thread Raw
In response to Re: A single escape required for log_filename  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
* Joshua D. Drake (jd@commandprompt.com) wrote:
> On Tue, 2009-01-13 at 16:58 -0500, Tom Lane wrote:
> > You might think you do, but it won't work with PG; external rotators
> > only work with programs that respond to SIGHUP by re-opening their log
> > files.
>
> copytruncate resolves this issue does it not? On that note it seems
> maybe that is a smart idea (to reopen the log). PostgreSQL will already
> allow you to arbitrarily change the log_filename with a HUP.

It would certainly be nice to have a way to cause PostgreSQL to reopen
it's log file without disrupting operation.  That's a much better option
than using copytruncate.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: A single escape required for log_filename
Next
From: Peter Eisentraut
Date:
Subject: So, what locale should the regression tests run in?