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

Re: way to turn off epochs in log_filename

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Lowry <dlowry(at)bju(dot)edu>, pgsql-admin(at)postgresql(dot)org
Subject: Re: way to turn off epochs in log_filename
Date: 2007-10-26 22:42:02
Message-ID: 20071026154202.501e9b75@scratch (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On Fri, 26 Oct 2007 17:45:00 -0400
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:
> >> If logrotate would work, we'd never have bothered writing our own
> >> substitute.  But there's no way for logrotate to repoint
> >> postmaster's stderr into other files.
> > Uh... can't we just use copytruncate with logroate?
> How's that going to reset the offsets in the stderr file descriptors
> of the various PG processes?  There might be some platforms and
> configurations where it will work, but I wouldn't tout it as a
> portable approach.  I'd also suppose that there are race conditions
> involved: you'll either lose or duplicate messages that are emitted
> while copytruncate works.

Yeah, we have seen that, where the log will be missing a few
statements. Good point.

Joshua D. Drake

> 			regards, tom lane


      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564   24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997
Donate to the PostgreSQL Project:
PostgreSQL Replication:

In response to


pgsql-admin by date

Next:From: Tom LaneDate: 2007-10-26 23:09:00
Subject: Re: Find the Person Connected to a Database
Previous:From: Naomi WalkerDate: 2007-10-26 22:25:17
Subject: Find who is connected to a database

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