X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BE48853430 for ; Tue, 19 Apr 2005 11:32:24 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 02028-03 for ; Tue, 19 Apr 2005 14:32:20 +0000 (GMT) Received: from mail.deg.cc (mail.deg.cc [64.139.134.201]) by svr1.postgresql.org (Postfix) with ESMTP id AF82653429 for ; Tue, 19 Apr 2005 11:32:17 -0300 (ADT) Received: from deg.cc (unknown [205.242.255.66]) by mail.deg.cc (Postfix) with ESMTP id 09351560C2; Tue, 19 Apr 2005 10:32:20 -0400 (EDT) Message-ID: <42651675.4020107@deg.cc> Date: Tue, 19 Apr 2005 10:32:21 -0400 From: Pallav Kalva User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040308 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin Subject: Re: Postgres Log rotation not working in 8.0.2 References: <4264097D.7090808@deg.cc> <25685.1113857543@sss.pgh.pa.us> <42642131.60603@deg.cc> <26045.1113859817@sss.pgh.pa.us> <42650AC4.3010902@deg.cc> <21270.1113920596@sss.pgh.pa.us> In-Reply-To: <21270.1113920596@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200504/263 X-Sequence-Number: 17276 Tom Lane wrote: >Pallav Kalva writes: > > >>Tom Lane wrote: >> >> >>>What I suspect happened is that it rotated last Thursday midnight, but >>>since %U hadn't changed since Monday, it overwrote the same file it was >>>using before. Check to see what the oldest entry in the file is ... >>> >>> >>> >> It didnt overwrite the file, the last log entry on the file is from >>2005-04-11 which is last monday. >> >> > >You mean the server hasn't actually emitted any messages since last >Monday? I think it only considers rotating the file when it actually >has something to write in it ... > > > I am sorry for the confusion, what i meant was the oldest entry on the log file was on last monday and most recent was this morning and the file didnt rotate yet.