But surely if the rotation is disabled, PostgreSQL will just append to the
log if it exists (hence the extra option of "truncate on rotation?")
Many services use a single log file and just keep adding to it - that's the
way I'd prefer to set PostgreSQL up, simply so I can predict what the log
file's name is. Our rotation system will then rotate the log and keep the
name in the same format as all our other services.
On 1/11/08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> > Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> You don't really have any choice about the matter --- Postgres will
> >> not use a single fixed filename because that would be guaranteed to
> >> lose log entries across a rotation.
> Unless he is using syslog?
> True, if you really dislike the way that the built-in log collector
> works, syslog is probably your best alternative.
> regards, tom lane
In response to
pgsql-admin by date
|Next:||From: Andreas Haumer||Date: 2008-01-12 16:25:45|
|Subject: Re: Restore dump into different databases/owners|
|Previous:||From: Andreas Haumer||Date: 2008-01-12 12:44:55|
|Subject: Restore dump into different databases/owners|