Skip site navigation (1) Skip section navigation (2)

Re: [PERFORM] temporary indexes

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>,<pgsql-hackers(at)postgresql(dot)org>,<pgsql-performance(at)postgresql(dot)org>
Subject: Re: [PERFORM] temporary indexes
Date: 2006-02-28 18:16:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-performance
>>> On Tue, Feb 28, 2006 at 12:06 pm, in message
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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


In response to

pgsql-performance by date

Next:From: Jim C. NasbyDate: 2006-02-28 21:02:32
Subject: Re: [PERFORM] temporary indexes
Previous:From: Steinar H. GundersonDate: 2006-02-28 18:08:37
Subject: Re: [HACKERS] temporary indexes

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-02-28 18:24:31
Subject: Re: [HACKERS] how solve diff of API counstruct_md_array between
Previous:From: Bruce MomjianDate: 2006-02-28 18:12:41
Subject: Re: Dead Space Map

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group