Re: BUG #3500: Horrible performance when wrong type is set in prepared statement

Flavio Botelho wrote:

> I know the application should not be doing this. But i wonder if lots of the
> complaints about postgres performance couldnt be related to problems like
> this. I suggest that you change the behaviour of something like that from
> silently accepting the string value to throwing an error.
> 
Well that would be bad.  I still have a lot of code with numbers inside 
quotes to work around the old postgres bug where index scans weren't 
used unless the numbers were in quotes (because the table columns were 
int2's and passed in numbers were assumed to be ints)

Do you have EXPLAIN output showing the difference in your queries if the 
values are in strings or not?