From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
Cc: | Mike Winter <mike(dot)winter(at)frontlogic(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: "SELECT IN" Still Broken in 7.4b |
Date: | 2003-08-20 20:41:32 |
Message-ID: | 1061412091.40948.65.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
On Wed, 2003-08-20 at 17:41, Stephan Szabo wrote:
> On Wed, 20 Aug 2003, Rod Taylor wrote:
>
> > > Thanks, Stephan. I was really hoping that the IN(valuelist) was going to
> > > be changed at the same time, because it really is unusable for anything
> > > over a couple of thousand values.
> >
> > Changed to do what?
>
> One possibility might be to act as if the valuelist was a table and do the
> IN as if it were that way, rather than treating it as a set of ORs. That
> would be basically like doing the temporary table solution, but without
> requiring the user to do it.
Is the temp table version any faster? I realize it has a higher limit
to the number of items you can have in the list.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-20 20:49:21 | Re: Buglist |
Previous Message | Jan Wieck | 2003-08-20 20:10:31 | Re: Buglist |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-20 20:53:22 | Re: Before/After Trigger User Switching |
Previous Message | Aasmund Midttun Godal | 2003-08-20 20:33:43 | Re: Before/After Trigger User Switching |