Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E597B9FC5D5 for ; Fri, 26 Oct 2007 18:39:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 24798-06 for ; Fri, 26 Oct 2007 18:39:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 356D89FA3C1 for ; Fri, 26 Oct 2007 18:39:20 -0300 (ADT) Received: from scratch (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l9QLdL1r028467; Fri, 26 Oct 2007 14:39:21 -0700 Date: Fri, 26 Oct 2007 14:40:05 -0700 From: "Joshua D. Drake" To: Tom Lane Cc: David Lowry , pgsql-admin@postgresql.org Subject: Re: way to turn off epochs in log_filename Message-ID: <20071026144005.3aa6cc29@scratch> In-Reply-To: <26960.1193434395@sss.pgh.pa.us> References: <26960.1193434395@sss.pgh.pa.us> Organization: Joshua D. Drake X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.0; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/_9ZAfeWr5U4o/c=kTIfm2bN"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Virus-Scanned: ClamAV 0.91.1/4598/Thu Oct 25 23:52:26 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Fri, 26 Oct 2007 14:39:22 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/269 X-Sequence-Number: 27183 --Sig_/_9ZAfeWr5U4o/c=kTIfm2bN Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 26 Oct 2007 17:33:15 -0400 Tom Lane wrote: > David Lowry writes: > > The docs state that if there are no %-escapes in log_filename, > > then it will add the epoch onto the end of the log filename. Is > > there any way to turn off this behavior and just use the filename > > specified in log_filename? I'd like have all the log data written > > to a file like postgresql.log and let logrotate do the rotation. >=20 > 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? That way we don't have to repoint. That is how we do it anyway... Or am I missing something? Joshua D. Drake >=20 > regards, tom lane >=20 > ---------------------------(end of > broadcast)--------------------------- TIP 1: if posting/reading > through Usenet, please send an appropriate subscribe-nomail command > to majordomo@postgresql.org so that your message can get through to > the mailing list cleanly >=20 --=20 =3D=3D=3D The PostgreSQL Company: Command Prompt, Inc. =3D=3D=3D Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240 PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ --Sig_/_9ZAfeWr5U4o/c=kTIfm2bN Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHIl61ATb/zqfZUUQRAm9dAJ92B7dvptCLOTmEFvM6i15Ud+YbIACgnfcb WESTRnFUVPSKu934nTOfI+s= =LYoX -----END PGP SIGNATURE----- --Sig_/_9ZAfeWr5U4o/c=kTIfm2bN--