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 B3F1ED1B285 for ; Tue, 20 Jul 2004 14:07:03 -0300 (ADT) 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 15852-03 for ; Tue, 20 Jul 2004 17:07:01 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id 9701CD1B2D9 for ; Tue, 20 Jul 2004 14:07:00 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 5827699; Tue, 20 Jul 2004 10:08:11 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: "Steinar H. Gunderson" , pgsql-performance@postgresql.org Subject: Re: Odd sorting behaviour Date: Tue, 20 Jul 2004 10:06:08 -0700 User-Agent: KMail/1.4.3 References: <20040708101913.GA15871@uio.no> <20040715120854.GA31259@uio.no> <20040720115116.GB19633@uio.no> In-Reply-To: <20040720115116.GB19633@uio.no> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200407201006.08649.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: 200407/130 X-Sequence-Number: 7521 Steinar, > I've tried some further tweaking, but I'm still unable to force it into > doing a hash join -- any ideas how I can find out why it chooses a merge > join? Actually, quick question -- have you tried setting enable_mergjoin=false to see the plan the system comes up with? Is it in fact faster? -- Josh Berkus Aglio Database Solutions San Francisco