X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 656D2475AFF for ; Mon, 3 Mar 2003 17:37:29 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 19121-10 for ; Mon, 3 Mar 2003 17:37:28 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 0705247611A for ; Mon, 3 Mar 2003 17:08:35 -0500 (EST) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2878041; Mon, 03 Mar 2003 14:08:16 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Michael Nachbaur , pgsql-sql@postgresql.org Subject: Re: Forcing query to use an index Date: Mon, 3 Mar 2003 14:09:04 -0800 X-Mailer: KMail [version 1.4] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200303031409.04345.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new X-Archive-Number: 200303/93 X-Sequence-Number: 12133 Michael, > Unfortunately one stage in the query keeps using a sequence scan rather= =20 > than the index. Here is the "EXPLAIN ANALYZE" results for the 115 line= =20 > SQL query. If you want any help, you'll need to post the query as well as the explain= =20 results. --=20 -Josh Berkus Aglio Database Solutions San Francisco