On 12.05.2005, at 16:15, Tom Lane wrote:
David Teran <[EMAIL PROTECTED]> writes:
Any hint how
to force postgres to use the index even with more OR parts?
More up-to-date statistics would evidently help; the thing is
estimating
hundreds of rows returned and actually finding none.
I always do a 'va
David Teran <[EMAIL PROTECTED]> writes:
> Any hint how
> to force postgres to use the index even with more OR parts?
More up-to-date statistics would evidently help; the thing is estimating
hundreds of rows returned and actually finding none.
regards, tom lane
--
Hi,
postgres 8.0.1, mac os x 10.3.9
i have a select with multiple OR's combined with one AND:
explain analyze SELECT t0.ATTRIBUTE_TYPE FROM ATTRIBUTE_VALUE t0 WHERE
(((t0.ATTRIBUTE_TYPE = 'pb'::varchar(10) OR t0.ATTRIBUTE_TYPE =
'po'::varchar(10) OR t0.ATTRIBUTE_TYPE = 'pn'::varchar(10) OR
t0.AT