Re: "SELECT IN" Still Broken in 7.4b
| От | Dani Oderbolz |
|---|---|
| Тема | Re: "SELECT IN" Still Broken in 7.4b |
| Дата | |
| Msg-id | 3F44995A.8040308@ecologic.de обсуждение исходный текст |
| Ответ на | Re: "SELECT IN" Still Broken in 7.4b (Stephan Szabo <sszabo@megazone.bigpanda.com>) |
| Ответы |
Re: "SELECT IN" Still Broken in 7.4b
|
| Список | pgsql-sql |
Stephan Szabo wrote: >On Wed, 20 Aug 2003, Rod Taylor wrote: >... > > >>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. >> >> > >Within the scope of the new hashed IN stuff I believe so in at least some >cases. I have a few million row table of integers where searching for >values IN (~10000 values) takes longer than creating the temp table, >copying into it and doing the in subquery. That's not a particularly >meaningful test case, but sending the psql output to /dev/null gives me: ... > But where do your values come from in the first place? Couldn't you optimize your model so that you don't have to copy around such amounts of data? Regards, Dani
В списке pgsql-sql по дате отправления: