Re: IN operator causes sequential scan (vs. multiple OR expressions) - Mailing list pgsql-performance

From Ryan Holmes
Subject Re: IN operator causes sequential scan (vs. multiple OR expressions)
Date
Msg-id D963734A-D30D-416A-A255-DC70B66CA727@hyperstep.com
Whole thread Raw
In response to Re: IN operator causes sequential scan (vs. multiple OR expressions)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
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 changes are no problem.

Thanks,
-Ryan


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: IN operator causes sequential scan (vs. multiple OR expressions)
Next
From: "Dave Dutcher"
Date:
Subject: Re: Bad Row Count Estimate on View with 8.2