From: | Jeff Eckermann <jeckermann(at)verio(dot)net> |
---|---|
To: | "'Zak McGregor'" <zak(at)mighty(dot)co(dot)za>, pgsql-general(at)postgresql(dot)org |
Subject: | RE: Large OR query |
Date: | 2001-06-12 13:37:33 |
Message-ID: | 08CD1781F85AD4118E0800A0C9B8580B094AD2@NEZU |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I would load the 1000 values into a temporary table, and join on the ID
field. I usually find that approach gives much faster results.
> -----Original Message-----
> From: Zak McGregor [SMTP:zak(at)mighty(dot)co(dot)za]
> Sent: Tuesday, June 12, 2001 7:42 AM
> To: pgsql-general(at)postgresql(dot)org
> Subject: [GENERAL] Large OR query
>
> Hi all
>
> If I have say 1000 values for an ID field, what is the best way to
> select from a table all the corresponding records?
> I have tried
> select * from blah where id in (id1,id2,id3...id1000)
> and
> select * from blah where id=id1 or id=id2 ... or id=id1000
>
> and both are pretty slow.
> Is there a better way to do this please?
>
> Thanks
>
> Ciao
> --
> Zak McGregor http://www.carfolio.com - Over 7000 car specs online
> Web mercenary - currently for hire. Perl/html/.js/sql/cgi/GNUlinux/php +
> ---------------------------------------------------------------------
> "Trying to make bits uncopyable is like trying to make water not wet.
> The sooner people accept this, and build business models that take
> this into account, the sooner people will start making money again."
> -- Bruce Schneier
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-06-12 13:47:00 | Re: [NOVICE] PostgreSQL problem with functions |
Previous Message | Martín Marqués | 2001-06-12 12:53:22 | Re: [SQL] ORDER BY what? |