Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id E542B9F995D for ; Fri, 26 Oct 2007 18:45:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 14512-06 for ; Fri, 26 Oct 2007 18:45:05 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D934D9F9DB6 for ; Fri, 26 Oct 2007 18:45:04 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l9QLj0Je027414; Fri, 26 Oct 2007 17:45:00 -0400 (EDT) To: "Joshua D. Drake" cc: David Lowry , pgsql-admin@postgresql.org Subject: Re: way to turn off epochs in log_filename In-reply-to: <20071026144005.3aa6cc29@scratch> References: <26960.1193434395@sss.pgh.pa.us> <20071026144005.3aa6cc29@scratch> Comments: In-reply-to "Joshua D. Drake" message dated "Fri, 26 Oct 2007 14:40:05 -0700" Date: Fri, 26 Oct 2007 17:45:00 -0400 Message-ID: <27413.1193435100@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/270 X-Sequence-Number: 27184 "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. > 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. regards, tom lane