Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 626449FCCF9 for ; Fri, 26 Oct 2007 18:33:30 -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 12971-03-2 for ; Fri, 26 Oct 2007 18:33:11 -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 A80089FCD36 for ; Fri, 26 Oct 2007 18:33:18 -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 l9QLXFg3026961; Fri, 26 Oct 2007 17:33:15 -0400 (EDT) To: David Lowry cc: pgsql-admin@postgresql.org Subject: Re: way to turn off epochs in log_filename In-reply-to: References: Comments: In-reply-to David Lowry message dated "Fri, 26 Oct 2007 14:10:58 -0400" Date: Fri, 26 Oct 2007 17:33:15 -0400 Message-ID: <26960.1193434395@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/268 X-Sequence-Number: 27182 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. 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. regards, tom lane