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 330265E471A; Wed, 1 Sep 2004 07:06:32 -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 94058-08; Wed, 1 Sep 2004 10:06:23 +0000 (GMT) Received: from tino.sinectis.com.ar (tino.sinectis.com.ar [216.244.192.232]) by svr1.postgresql.org (Postfix) with ESMTP id 18AC45E4711; Wed, 1 Sep 2004 07:06:20 -0300 (ADT) Received: by tino.sinectis.com.ar (Postfix, from userid 99) id 501786C4EA; Wed, 1 Sep 2004 07:06:22 -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 Subject: slower every day Cc: pgsql-admin@postgresql.org Reply-To: gbarosio@uolsinectis.com.ar Message-Id: <20040901100622.501786C4EA@tino.sinectis.com.ar> Date: Wed, 1 Sep 2004 07:06:22 -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/1 X-Sequence-Number: 14704 Dear all, I am currently experiencing troubles with the performance of my critical's database. 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. Today I am in the same situation again. The only change that I've done was a highest level of debug in the conf file (loggin lot of stuff). I understand that this could lack on performance, but when I've changed the .conf file to the usual .conf file (with less debug), and pg_ctl reload(ed) it, it goes on debuging as in the first state, in the higher level. Is this a known issue? My conclusion is that I can aquire high levels of debug while the server is running, editing the .conf file, and pg_reload(ing) it, but I can go back then, unless I pg_restart the server. Is this ok? Some info ----------------------------------------------------------- PostgreSQL 7.4.2 [postgres@lmnukmis02 data]$ pg_config --configure '--enable-thread-safety' '--with-perl' Intel(R) Xeon(TM) MP CPU 2.80GHz Linux 2.4.24-ck1 #5 SMP Fri Mar 12 23:41:51 GMT 2004 i686 unknown RAM 4 Gb. ----------------------------------------------------------- Thanks, Guido.