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 988F49DCA1B for ; Tue, 28 Feb 2006 14:08:26 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 79779-03 for ; Tue, 28 Feb 2006 14:08:23 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from cassarossa.samfundet.no (cassarossa.samfundet.no [129.241.93.19]) by postgresql.org (Postfix) with ESMTP id 085279DCAB9 for ; Tue, 28 Feb 2006 14:08:20 -0400 (AST) Received: from trofast.ipv6.sesse.net ([2001:700:300:dc03:20e:cff:fe36:a766] helo=trofast.sesse.net) by cassarossa.samfundet.no with esmtp (Exim 4.50) id 1FE9Gk-0001GJ-W3 for pgsql-performance@postgresql.org; Tue, 28 Feb 2006 19:08:19 +0100 Received: from sesse by trofast.sesse.net with local (Exim 3.36 #1 (Debian)) id 1FE9H3-0000QM-00 for ; Tue, 28 Feb 2006 19:08:37 +0100 Date: Tue, 28 Feb 2006 19:08:37 +0100 From: "Steinar H. Gunderson" To: pgsql-performance@postgresql.org Subject: Re: [HACKERS] temporary indexes Message-ID: <20060228180837.GA1593@uio.no> Mail-Followup-To: pgsql-performance@postgresql.org References: <44041B68.EE98.0025.0@wicourts.gov> <20060228164515.GS82012@pervasive.com> <20060228164515.GS82012@pervasive.com> <16076.1141146348@sss.pgh.pa.us> <440435BC.EE98.0025.0@wicourts.gov> <44043A34.EE98.0025.0@wicourts.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <44043A34.EE98.0025.0@wicourts.gov> X-Operating-System: Linux 2.6.14.3 on a x86_64 X-Message-Flag: Outlook? --> http://www.mozilla.org/products/thunderbird/ User-Agent: Mutt/1.5.11+cvs20060126 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.083 required=5 tests=[AWL=0.083] X-Spam-Score: 0.083 X-Spam-Level: X-Archive-Number: 200602/441 X-Sequence-Number: 17427 On Tue, Feb 28, 2006 at 11:55:32AM -0600, Kevin Grittner wrote: >> Also, EXISTS works in situations where >> you need to compare on multiple columns, so it is useful in many >> situations where EXISTS or MIN/MAX techniques just don't work. > Sorry. That should have read: > > EXISTS works in situations where > you need to compare on multiple columns, so it is useful in many > situations where IN or MIN/MAX techniques just don't work. Can't you just do WHERE (foo,bar) IN ( SELECT baz,quux FROM table )? I'm quite sure I've done that a number of times. /* Steinar */ -- Homepage: http://www.sesse.net/