X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 08A309DCC55; Tue, 28 Feb 2006 14:17:02 -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 81310-04; Tue, 28 Feb 2006 14:17:01 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by postgresql.org (Postfix) with ESMTP id E55C79DCC08; Tue, 28 Feb 2006 14:16:56 -0400 (AST) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Tue, 28 Feb 2006 12:16:57 -0600 Message-Id: <44043F32.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0 Date: Tue, 28 Feb 2006 12:16:50 -0600 From: "Kevin Grittner" To: "Tom Lane" Cc: "Jim C. Nasby" , , Subject: Re: [PERFORM] temporary indexes 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><44043A34.EE98.0025.0@wicourts.gov> <16797.1141150016@sss.pgh.pa.us> In-Reply-To: <16797.1141150016@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.081 required=5 tests=[AWL=0.081] X-Spam-Score: 0.081 X-Spam-Level: X-Archive-Number: 200602/1231 X-Sequence-Number: 80369 >>> On Tue, Feb 28, 2006 at 12:06 pm, in message <16797.1141150016@sss.pgh.pa.us>, Tom Lane wrote: > IN works fine on multiple columns: > > (foo, bar, baz) IN (SELECT x, y, z FROM ...) Thanks for pointing that out. I recognize it as valid ANSI/ISO syntax, using a row value constructor list. Unfortunately, row value constructor lists failed to make the portability cut for allowed syntax here, because it was not supported by all candidate products at the time. It is still not supported by the product we're moving from, and we'll have about a one year window when our code will need to run on both. -Kevin