The only case that I think still has any merit is where you get a
significantly better plan with known parameter values than without.
The projected-cost threshold might be a reasonable approach for
attacking that, ie, if estimated cost of generic plan exceeds X
then take the time to build a
http://developer.postgresql.org/pgdocs/postgres/release-9-0.html
Performance section:
Simplify the forms foo true and foo false to foo = false and
foo = true during query optimization.
Will it work correct;ly when foo is NULL?
--
Sent via pgsql-hackers mailing list
On Feb 26, 2010, at 0:55 , Дмитрий Фефелов wrote:
http://developer.postgresql.org/pgdocs/postgres/release-9-0.html
Performance section:
Simplify the forms foo true and foo false to foo = false and
foo = true during query optimization.
Will it work correct;ly when foo is NULL
