Yuri Levinsky wrote
>> We have two equals queries where the sole difference is in the limit.
>> - The first is hard coded with limit 500.
>> - The second is prepared with limit $1 ($1 is bound to 500).
>
>
>> PostgreSQL give us two different plans with a huge execution time for
>> the
> prepared
Amit,
It's very strength for me to hear that PostgreSQL generate execution plan for
prepared statements during execution, I always was thinking that the purpose of
the prepared statement is to eliminate such behavior. Can it lead to some
performance degradation in case of heavy "update batch",
