Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id F07BB2E3101 for ; Sat, 12 Jan 2008 12:18:16 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 85513-01 for ; Sat, 12 Jan 2008 12:18:14 -0400 (AST) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.184]) by postgresql.org (Postfix) with ESMTP id 990A52E3004 for ; Sat, 12 Jan 2008 12:18:10 -0400 (AST) Received: by rv-out-0910.google.com with SMTP id l15so1519961rvb.43 for ; Sat, 12 Jan 2008 08:18:08 -0800 (PST) Received: by 10.141.198.9 with SMTP id a9mr2726253rvq.280.1200154688088; Sat, 12 Jan 2008 08:18:08 -0800 (PST) Received: by 10.140.171.12 with HTTP; Sat, 12 Jan 2008 08:18:08 -0800 (PST) Message-ID: <33671a790801120818i31f126b9ueac31f33ddb23063@mail.gmail.com> Date: Sat, 12 Jan 2008 16:18:08 +0000 From: "Andy Shellam" To: pgsql-admin@postgresql.org Subject: Re: 8.3 RC1 - Logging and filenames In-Reply-To: <12963.1200011400@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4277_12379164.1200154688095" References: <33671a790801101445j7f3c8644wf41c1e6fced8bedc@mail.gmail.com> <12716.1200010137@sss.pgh.pa.us> <20080110162258.4b0d4991@commandprompt.com> <12963.1200011400@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/130 X-Sequence-Number: 27904 ------=_Part_4277_12379164.1200154688095 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all, 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. Andy On 1/11/08, Tom Lane wrote: > > "Joshua D. Drake" writes: > > Tom Lane 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 > ------=_Part_4277_12379164.1200154688095 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all,

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.

Andy

On 1/11/08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Joshua D. Drake" <jd@commandprompt.com> writes:
> Tom Lane <tgl@sss.pgh.pa.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

------=_Part_4277_12379164.1200154688095--