Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 991979FB3D4 for ; Mon, 2 Oct 2006 13:35:50 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 24781-07 for ; Mon, 2 Oct 2006 13:35:35 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by postgresql.org (Postfix) with ESMTP id 672099FB1DA for ; Mon, 2 Oct 2006 13:35:35 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id t13so1835710wxc for ; Mon, 02 Oct 2006 09:35:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=RDy5YLCTHG9TzQ2thkwMoXjpjVi+Z6/X0mCyTvZfqfwCkgjYq3NauFPSJC6X6A4pXPYold4vy5h5X1O6r+Cxkc/3SQ1QOKlbQk2pIYUrfBTmYbVtsCoQ3RghE7sxas1Hu4ujjd21vxnJHqoPU5sG07imgL9z0nOjk4T2bDBTles= Received: by 10.90.51.17 with SMTP id y17mr2954910agy; Mon, 02 Oct 2006 09:35:34 -0700 (PDT) Received: by 10.90.81.4 with HTTP; Mon, 2 Oct 2006 09:35:34 -0700 (PDT) Message-ID: Date: Mon, 2 Oct 2006 21:35:34 +0500 From: "Shoaib Mir" To: "Pallav Kalva" Subject: Re: Postgres Logging doesnt work Cc: "Andrew Sullivan" , pgsql-admin@postgresql.org In-Reply-To: <45213CF0.90009@livedatagroup.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_78889_11570325.1159806934390" References: <45212A6B.2060503@livedatagroup.com> <20061002161255.GC32410@phlogiston.dyndns.org> <45213CF0.90009@livedatagroup.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.451 tagged_above=0 required=5 tests=AWL, HTML_30_40, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200610/7 X-Sequence-Number: 23310 ------=_Part_78889_11570325.1159806934390 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I guess that might work: 1. Set the following in postgresql.conf file --> log_rotation_age = 1 2. rename the already present log file from dbserver logs folder 3. Now do --> pg_ctl reload (so that log_rotation_age change you did comes in affect) 4. Check the log folder after a while (after 1 minutes) and it will be having a new log file and doing all the logging there 5. After it starts the logging you can revert the change done to rotation_age and do a reload again. Thanks, --- Shoaib Mir EnterpriseDB (www.enterprisedb.com) On 10/2/06, Pallav Kalva wrote: > > Hi Andrew, > > Thanks! for the reply, it is a small file. the file size on it is > 735K that's pretty small. Not sure why it stopped writing to the log > file, is there any way to start logging without starting postgres ? > > Pallav. > > Andrew Sullivan wrote: > > On Mon, Oct 02, 2006 at 11:04:11AM -0400, Pallav Kalva wrote: > > > >> Hi , > >> > >> My production database stopped writting to the postgres log files > >> all of a sudden, does anybody know why ? > >> > > > > How big is the file? > > > > > >> log_rotation_age | 10080 > >> log_rotation_size | 0 > >> > > > > You've set this up to rotate once every 10,080 minutes, no matter > > what. If you've run into a file size limit, then you'll be out of > > luck until the next file is opened, which should be on the same day > > of the week the postmaster was last started. Just a guess. > > > > A > > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > ------=_Part_78889_11570325.1159806934390 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I guess that might work:

1. Set the following in postgresql.conf file --> log_rotation_age = 1
2. rename the already present log file from dbserver logs folder
3. Now do --> pg_ctl reload (so that log_rotation_age change you did comes in affect)
4. Check the log folder after a while (after 1 minutes) and it will be having a new log file and doing all the logging there
5. After it starts the logging you can revert the change done to rotation_age and do a reload again.

Thanks,
---
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)



On 10/2/06, Pallav Kalva <pkalva@livedatagroup.com> wrote:
Hi Andrew,

     Thanks! for the reply, it is a small file. the file size on it is
735K that's pretty small. Not sure why it stopped writing to the log
file, is there any way to start logging without starting postgres ?

Pallav.

Andrew Sullivan wrote:
> On Mon, Oct 02, 2006 at 11:04:11AM -0400, Pallav Kalva wrote:
>
>> Hi ,
>>
>>     My production database stopped writting to the postgres log files
>> all of a sudden, does anybody know why ?
>>
>
> How big is the file?
>
>
>>  log_rotation_age               | 10080
>>  log_rotation_size              | 0
>>
>
> You've set this up to rotate once every 10,080 minutes, no matter
> what.  If you've run into a file size limit, then you'll be out of
> luck until the next file is opened, which should be on the same day
> of the week the postmaster was last started.  Just a guess.
>
> A
>
>


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

------=_Part_78889_11570325.1159806934390--