On Sat, 12 Mar 2005, Tom Lane wrote:
"Sergey E. Koposov" <[EMAIL PROTECTED]> writes:I want to descibe some strange behaviour of the postgres planner.
It's not strange exactly: the mechanism for OR indexscan and the mechanism for nestloop join indexscan are separate and don't talk to each other. So you don't get to have a join inner indexscan that involves an OR condition.
I have some vague ideas about replacing orindxpath.c entirely, once we have some infrastructure for doing OR indexscans via bitmap union. But it's not just around the corner.
for 8.1, probably ?
In the meantime you might try expressing your query as a UNION.
Hmm, I'm wondering if the table will be reades as much as the number of UNIONs or there is some optimization ?
regards, tom lane
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Regards, Oleg _____________________________________________________________ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
