| 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: | 44043F32.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
>>> On Tue, Feb 28, 2006 at 12:06 pm, in message
<16797(dot)1141150016(at)sss(dot)pgh(dot)pa(dot)us>,
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
both.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-02-28 18:24:31 | Re: [HACKERS] how solve diff of API counstruct_md_array between |
| Previous Message | Bruce Momjian | 2006-02-28 18:12:41 | Re: Dead Space Map |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-02-28 21:02:32 | Re: [PERFORM] temporary indexes |
| Previous Message | Steinar H. Gunderson | 2006-02-28 18:08:37 | Re: [HACKERS] temporary indexes |