On Jan 27, 2007, at 5:56 PM, Tom Lane wrote:
I've committed a fix for 8.2.2, but in the meantime maybe you could
change your varchar column to text?
regards, tom lane
Thank you for the help and the fix. We're just performance testing
right now so minor data model chan
Ryan Holmes <[EMAIL PROTECTED]> writes:
> So, yes, disabling seqscan does force an index scan for the IN
> version. My question now is, how do I get PostgreSQL to make the
> "right" decision without disabling seqscan?
I pinged you before because in a trivial test case I got
indexscans out of b
On Jan 27, 2007, at 3:53 PM, Tom Lane wrote:
Ryan Holmes <[EMAIL PROTECTED]> writes:
I have a relatively simple query where the planner chooses a
sequential scan when using the IN operator but chooses an index scan
when using logically equivalent multiple OR expressions.
EXPLAIN ANALYZE for
Ryan Holmes <[EMAIL PROTECTED]> writes:
> I have a relatively simple query where the planner chooses a
> sequential scan when using the IN operator but chooses an index scan
> when using logically equivalent multiple OR expressions.
EXPLAIN ANALYZE for both, please?
If you set enable_seqscan
PostgreSQL version: 8.2.1
OS: Windows Server 2003
I have a relatively simple query where the planner chooses a
sequential scan when using the IN operator but chooses an index scan
when using logically equivalent multiple OR expressions. Here is the
table structure and the two versions of th
