Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 721A59FA642 for ; Fri, 26 Oct 2007 19:41:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 91278-07 for ; Fri, 26 Oct 2007 19:41:15 -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 1CEE09FA5E3 for ; Fri, 26 Oct 2007 19:41:18 -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 l9QMfJEs030512; Fri, 26 Oct 2007 15:41:19 -0700 Date: Fri, 26 Oct 2007 15:42:02 -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: <20071026154202.501e9b75@scratch> In-Reply-To: <27413.1193435100@sss.pgh.pa.us> References: <26960.1193434395@sss.pgh.pa.us> <20071026144005.3aa6cc29@scratch> <27413.1193435100@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_/AjGFbNwOUjA6mZ4TQlOUwzB"; 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 15:41:20 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/274 X-Sequence-Number: 27188 --Sig_/AjGFbNwOUjA6mZ4TQlOUwzB Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 26 Oct 2007 17:45:00 -0400 Tom Lane wrote: > "Joshua D. Drake" writes: > > Tom Lane 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. >=20 > > Uh... can't we just use copytruncate with logroate? >=20 > 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 >=20 > regards, tom lane >=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_/AjGFbNwOUjA6mZ4TQlOUwzB Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHIm07ATb/zqfZUUQRAlu2AJ0VmF7cnzPBDcrR4wmxm37cl89nngCgrtzs LTmA42K6q0wsm2GkLAd89v4= =gT7r -----END PGP SIGNATURE----- --Sig_/AjGFbNwOUjA6mZ4TQlOUwzB--