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 E093C5E4711; Wed, 1 Sep 2004 07:57: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 08420-09; Wed, 1 Sep 2004 10:57:14 +0000 (GMT) Received: from tino.sinectis.com.ar (tino.sinectis.com.ar [216.244.192.232]) by svr1.postgresql.org (Postfix) with ESMTP id 205415E46F9; Wed, 1 Sep 2004 07:57:12 -0300 (ADT) Received: by tino.sinectis.com.ar (Postfix, from userid 99) id 1489B6C4FD; Wed, 1 Sep 2004 07:57:15 -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: pgsql-performance@postgresql.org, pgsql-admin@postgresql.org Subject: Re: slower every day Reply-To: gbarosio@uolsinectis.com.ar Message-Id: <20040901105715.1489B6C4FD@tino.sinectis.com.ar> Date: Wed, 1 Sep 2004 07:57:15 -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/3 X-Sequence-Number: 14706 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? Regards, Guido > Am Mittwoch, 1. September 2004 12:06 schrieb G u i d o B a r o s i o: > > The problem is the time that the postgres takes to perform/return a > > query. For example, trying the \d command takes between 4 or 5 > > seconds. This table is very big, but I am not asking for the rows, only > > asking the table schema, so...why is this so slow?!?!? My last > > administrative action into this table was a reindex to all the indexes via > > the BKI in standalone mode. I thought I suceed, but this was las saturday. > > Do you regularly vacuum and analyze the database? > > -- > Peter Eisentraut > http://developer.postgresql.org/~petere/ > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend