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 DBE655E471A for ; Wed, 1 Sep 2004 11:28:15 -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 89163-07 for ; Wed, 1 Sep 2004 14:28:15 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by svr1.postgresql.org (Postfix) with SMTP id 1939D5E4722 for ; Wed, 1 Sep 2004 11:28:12 -0300 (ADT) Received: (qmail 8985 invoked by uid 65534); 1 Sep 2004 14:28:18 -0000 Received: from office01.emerion.com (EHLO zaphod) (83.64.50.26) by mail.gmx.net (mp017) with SMTP; 01 Sep 2004 16:28:18 +0200 X-Authenticated: #1946847 Message-ID: <01ae01c4902f$ed692490$ad01a8c0@zaphod> From: "Michael Paesold" To: , , References: <20040901105715.1489B6C4FD@tino.sinectis.com.ar> Subject: Re: slower every day Date: Wed, 1 Sep 2004 16:28:15 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/8 X-Sequence-Number: 14711 This issue was resently discussed on hackers. It is a known issue, not very convinient for the user. Nevertheless it is not fixed in 8.0, but will perhaps be addressed in the next major release. (Remembering, it was a non-trivial thing to change.) Best Regards, Michael Paesold G u i d o B a r o s i o wrote: > The solution appeared as something I didn't know > > On the .conf file > > Previous situation: > > #log_something=false > log_something=true > > Worst situation > #log_something=false > #log_something=true > > Nice situation > log_something=false > #log_something=true > > > Ok, the problem was that I assumed that commenting a value on > the conf file will set it up to a default (false?). I was wrong. > My server was writting tons of log's. > > Is this the normal behavior for pg_ctl reload? It seems that looks for new values, remembering the last state on the ones that actually are commented. Although it's my fault to have 2 (tow) lines for the same issue, and that I should realize that this is MY MISTAKE, the log defaults on a reload, if commented, tend to be the last value entered?