X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 3C9499FB1D7 for ; Wed, 23 Aug 2006 23:30:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 09419-04 for ; Wed, 23 Aug 2006 23:30:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id DB5DF9FA3D7 for ; Wed, 23 Aug 2006 23:30:23 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k7O2UGqx028099; Wed, 23 Aug 2006 22:30:18 -0400 (EDT) To: "Dan Langille" cc: Chris , pgsql-performance@postgresql.org Subject: Re: Forcing index usage without 'enable_hashjoin = FALSE' In-reply-to: <44ECD283.18248.1EF83D45@dan.langille.org> References: <44EA9190.5306.162A8DE9@dan.langille.org> <44ECD283.18248.1EF83D45@dan.langille.org> Comments: In-reply-to "Dan Langille" message dated "Wed, 23 Aug 2006 22:11:15 -0400" Date: Wed, 23 Aug 2006 22:30:16 -0400 Message-ID: <28098.1156386616@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.15 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/381 X-Sequence-Number: 20566 "Dan Langille" writes: > Without leaving "enable_hashjoin = false", can you suggest a way to > force the index usage? Have you tried reducing random_page_cost? FYI, 8.2 should be a bit better about this. regards, tom lane