From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PERFORM] Hypothetical suggestions for planner, indexing |
Date: | 2003-05-06 14:04:39 |
Message-ID: | 20030506220422.T16817-100000@houston.familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
> On Mon, May 05, 2003 at 09:33:33PM -0700, Josh Berkus wrote:
> > EXISTS is more flexible than IN; how can you do a 3-column corellation on an
> > IN clause?
>
> It would be nice to add support for multi-column IN..
>
> WHERE (a, b, c) IN (SELECT a, b, c ...)
Umm....we DO have that...
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-05-06 14:06:12 | Re: 7.4 features list |
Previous Message | Tom Lane | 2003-05-06 13:49:04 | Re: Installin Postgres |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2003-05-06 14:39:57 | Re: [ADMIN] A query with performance problems. |
Previous Message | Reiner Dassing | 2003-05-06 14:00:32 | Re: Select on timestamp-day slower than timestamp alone |