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 B77DA329D27 for ; Thu, 16 Sep 2004 22:04:33 +0100 (BST) 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 91020-04 for ; Thu, 16 Sep 2004 21:04:25 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id 91E7A329D15 for ; Thu, 16 Sep 2004 22:04:27 +0100 (BST) Received: from [64.81.245.111] (account josh@agliodbs.com HELO temoku.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6362549; Thu, 16 Sep 2004 14:05:47 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Qing Zhao Subject: Re: Question about PG on OSX Date: Thu, 16 Sep 2004 14:05:28 -0700 User-Agent: KMail/1.6.2 Cc: 'Postgresql Performance' References: <200409161050.33289.josh@agliodbs.com> <200409161200.32427.josh@agliodbs.com> <224B107D-0821-11D9-B278-000A95AB8896@supplyfx.com> In-Reply-To: <224B107D-0821-11D9-B278-000A95AB8896@supplyfx.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409161405.28778.josh@agliodbs.com> 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/176 X-Sequence-Number: 8304 Qing, Please don't start a new question by replying to someone else's e-mail. It confuses people and makes it unlikely for you to get help. > My suspicion is that since now a few indexes are added, every ops are > run by PostgreSQL with the indexes being used when calculating cost. > This leads to the downgrade of performance. That seems rather unlikely to me. Unless you've *really* complex queries and some unusual settings, you can't swamp the CPU through query planning. On the other hand, your mention of REINDEX indicates that the table is being updated very frequently. If that's the case, then the solution is probably for you to cut back on the number of indexes. -- --Josh Josh Berkus Aglio Database Solutions San Francisco