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 923C5D1B298 for ; Tue, 20 Jul 2004 08:51:25 -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 50819-01 for ; Tue, 20 Jul 2004 11:51:20 +0000 (GMT) Received: from trofast.sesse.net (trofast.sesse.net [129.241.93.32]) by svr1.postgresql.org (Postfix) with ESMTP id A2339D1B269 for ; Tue, 20 Jul 2004 08:51:13 -0300 (ADT) Received: from sesse by trofast.sesse.net with local (Exim 3.36 #1 (Debian)) id 1Bmt9Q-00058y-00 for ; Tue, 20 Jul 2004 13:51:16 +0200 Date: Tue, 20 Jul 2004 13:51:16 +0200 From: "Steinar H. Gunderson" To: pgsql-performance@postgresql.org Subject: Re: Odd sorting behaviour Message-ID: <20040720115116.GB19633@uio.no> References: <20040708101913.GA15871@uio.no> <200407141841.01863.josh@agliodbs.com> <16637.1089867158@sss.pgh.pa.us> <20040715120854.GA31259@uio.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040715120854.GA31259@uio.no> X-Operating-System: Linux 2.6.6 on a i686 User-Agent: Mutt/1.5.6+20040523i 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/124 X-Sequence-Number: 7515 On Thu, Jul 15, 2004 at 02:08:54PM +0200, Steinar H. Gunderson wrote: > sort_mem is already 16384, which I thought would be plenty -- I tried > increasing it to 65536 which made exactly zero difference. :-) 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? /* Steinar */ -- Homepage: http://www.sesse.net/