X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id DAEC511F684E
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Thu,  6 Apr 2006 21:09:37 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 92296-07
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Thu,  6 Apr 2006 21:09:31 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from globalrelay.com (mail1.globalrelay.com [216.18.71.77])
	by postgresql.org (Postfix) with ESMTP id 957D611F681A
	for <pgsql-performance@postgresql.org>;
	Thu,  6 Apr 2006 21:09:34 -0300 (ADT)
X-Virus-Scanned: Scanned by GRC-AntiVirus Gateway
X-GR-Acctd: YES
Received: from [67.90.96.2] (HELO DaveEMachine)
	by globalrelay.com (CommuniGate Pro SMTP 4.2.3)
	with ESMTP id 87429787; Thu, 06 Apr 2006 17:09:33 -0700
From: "Dave Dutcher" <dave@tridecap.com>
To: "'Brian Herlihy'" <btherl@yahoo.com.au>,
 <pgsql-performance@postgresql.org>
Subject: Re: Query planner is using wrong index.
Date: Thu, 6 Apr 2006 19:09:33 -0500
Message-ID: <00c101c659d7$8cc26a70$8300a8c0@tridecap.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-reply-to: <20060406235622.27528.qmail@web52307.mail.yahoo.com>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0 required=5 tests=[none]
X-Spam-Score: 0
X-Spam-Level: 
X-Archive-Number: 200604/122
X-Sequence-Number: 18206



> -----Original Message-----
> From: pgsql-performance-owner@postgresql.org
[mailto:pgsql-performance-
> owner@postgresql.org] On Behalf Of Brian Herlihy
> Sent: Thursday, April 06, 2006 6:56 PM
> To: pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] Query planner is using wrong index.
[Snip]
> I am really surprised that I have to go through such contortions just
to
> use
> the primary key!  This area of Postgres needs improvement.
> 


Of course you mentioned that you are using 7.4.7.  You might want to try
upgrading to 8.1.3.  There have been a lot of improvements to the
performance since 7.4. I don't know if your specific problem was fixed,
but it's worth a try.

Also you might want to at least upgrade to 7.4.12 for the bug fixes.