Re: A single escape required for log_filename

On Tue, 2009-01-13 at 16:58 -0500, Tom Lane wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> > I have perfectly good log rotation utility that exists on my OS. (yes I
> > am aware of the possibility of losing a log entry when using logrotate).
>
> 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.

> PostgreSQL will append the epoch of the new log file's creation
> time. For example, if log_filename were server_log, then the chosen file
> name would be server_log.1093827753 for a log starting at Sun Aug 29
> 19:02:33 2004 MST. This parameter can only be set in the postgresql.conf
> file or on the server command line.

O.k. at least its documented (will go peek at my info).

Joshua D. Drake

--
PostgreSQL
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997