2009/6/1 Koen Martens <pg...@metro.cx>

>
> Now, when I split up the OR in two distinct queries, everything is nice and
> fast. Both queries run in sub-second time.


Hi.

PostgreSQL simply do not like ORs (can't use indexes in this case), so
UNION/UNION ALL is your friend.

Best regards, Vitalii Tymchyshyn

Reply via email to