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 2D51B5E4713; Wed, 1 Sep 2004 12:07:46 -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 06944-09; Wed, 1 Sep 2004 15:07:43 +0000 (GMT) Received: from honorio.sinectis.com.ar (honorio.sinectis.com.ar [216.244.192.201]) by svr1.postgresql.org (Postfix) with ESMTP id 090945E3F15; Wed, 1 Sep 2004 12:07:34 -0300 (ADT) Received: by honorio.sinectis.com.ar (Postfix, from userid 99) id BB5206C4E8; Wed, 1 Sep 2004 12:07:39 -0300 (GMT+3) Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Mailer: Sinectis Webmail 5.6.16-1.5.1 From: G u i d o B a r o s i o To: mpaesold@gmx.at, pgsql-performance@postgresql.org, pgsql-admin@postgresql.org Subject: Re: slower every day Cc: pgsql-hackers@postgresql.org Reply-To: gbarosio@uolsinectis.com.ar Message-Id: <20040901150739.BB5206C4E8@honorio.sinectis.com.ar> Date: Wed, 1 Sep 2004 12:07:39 -0300 (GMT+3) 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/9 X-Sequence-Number: 14712 Thanks for the reply, Been reading hackers of Aug 2004 and found the threads. It's a common habit to create two lines on the configuration files, in order to maintain the copy of the default conf file. I guess this should be the worst scenery for a freshly incoming DBA trying to put things in order. A temporary patch, will be updating documentation, encouraging administrators to use the SHOW ALL; command in the psql env, to confirm that changes where made. In my case, a 1.2 gig file was written, performance was on the floor. And my previous situation, a reindex force task last saturday, confused me. This is not a trivial problem, but in conjunction with other small problems could become a big one. Good habits when touching conf files & using the SHOW ALL to confirm that changes where made will help until this is patched. Thanks for Postgres, Regards, Guido. > 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? >