On 6/26/08, Craig James <[EMAIL PROTECTED]> wrote: > This seems like a bug to me, but it shows up as a performance problem. > Since the column being queried is an integer, the second query (see below) > can't possibly match, yet Postgres uses a typecast, forcing a full table > scan for a value that can't possibly be in the table.
Which version are you using? 8.3 removes a lot of implicit casts (all? not sure), so this may already be your fix. Cheers, Frank -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
