X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 42C973A543E for ; Mon, 24 Jan 2005 10:39:01 +0000 (GMT) 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 89834-02 for ; Mon, 24 Jan 2005 10:38:53 +0000 (GMT) Received: from my.endian.it (unknown [62.146.87.34]) by svr1.postgresql.org (Postfix) with ESMTP id D198A3A53EF for ; Mon, 24 Jan 2005 10:38:50 +0000 (GMT) Received: from [192.168.1.6] (host77-118.pool80180.interbusiness.it [80.180.118.77]) (authenticated (0 bits)) by my.endian.it (8.11.6/8.11.6) with ESMTP id j0OBMOt28244; Mon, 24 Jan 2005 12:22:24 +0100 Subject: Re: poor performance of db? From: Chris Mair To: SpaceBallOne Cc: pgsql-performance@postgresql.org In-Reply-To: References: Content-Type: text/plain Message-Id: <1106563126.7157.51.camel@dell> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Mon, 24 Jan 2005 11:38:47 +0100 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200501/437 X-Sequence-Number: 10127 > I then re-wrote the page to use a single select query to call all the > information needed by PHP to draw the screen. That managed to shave it > down to 3.5 seconds... but this so far is as fast as I can get the > page to load. Have tried vacuuming and creating indexes but to no > avail. (increasing shared mem buffers yet to be done) If you call this select statement directly from psql instead of through the PHP thing, does timing change? (just to make sure, time is actually spent in the query and not somewhere else) PS: use \timing in psql to see timing information Bye, Chris.