Skip site navigation (1) Skip section navigation (2)

Re: 8.3 RC1 - Logging and filenames

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andy Shellam" <andy(dot)shellam-lists(at)mailnetwork(dot)co(dot)uk>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: 8.3 RC1 - Logging and filenames
Date: 2008-01-11 00:08:57
Message-ID: 12716.1200010137@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"Andy Shellam" <andy(dot)shellam-lists(at)mailnetwork(dot)co(dot)uk> writes:
> What I want PostgreSQL to do is put a log file "postgresql.log" in
> "/var/log/pgsql" - I have an application that handles log rotations, so
> would prefer to do it with that, rather than have PostgreSQL do the
> rotation.

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.

> I would have thought my config shown below would have made this happen, but
> it doesn't appear so.  Instead PostgreSQL creates a file called "
> postgresql.log.1200003749" in /var/log/pgsql.

> Best of it is, I cannot work out what those numbers mean.

Per the documentation, Postgres appends the Unix epoch of the file's
creation time if the given pattern hasn't got any %-escapes.
Looks like that corresponds to Thu Jan 10 2008, 17:22:29 EST.

			regards, tom lane

In response to

Responses

pgsql-admin by date

Next:From: Joshua D. DrakeDate: 2008-01-11 00:22:58
Subject: Re: 8.3 RC1 - Logging and filenames
Previous:From: Kevin KempterDate: 2008-01-10 23:08:48
Subject: Re: PITR warm-standby with 8.2 setup questions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group