Skip site navigation (1) Skip section navigation (2)

Re: Typecast bug?

From: "Frank Joerdens" <frank(at)joerdens(dot)de>
To: "Craig James" <craig_james(at)emolecules(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Typecast bug?
Date: 2008-06-26 07:02:13
Message-ID: 7d10d2df0806260002w8707ea1rf8f62ca8126099a8@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On 6/26/08, Craig James <craig_james(at)emolecules(dot)com> 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

In response to

Responses

pgsql-performance by date

Next:From: Guillaume SmetDate: 2008-06-26 07:12:56
Subject: Re: Typecast bug?
Previous:From: Craig JamesDate: 2008-06-26 06:22:20
Subject: Re: Typecast bug?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group