Re: Avoiding bad prepared-statement plans.
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Greg Stark <gsstark@mit.edu>
Cc: Bruce Momjian <bruce@momjian.us>, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Bart Samwel <bart@samwel.tk>, Jeroen Vermeulen <jtv@xs4all.nl>, pgsql-hackers@postgresql.org
Date: 2010-02-16T14:31:44Z
Lists: pgsql-hackers
> > Well using parameters will always have a better chance of producing a > better plan but that's not the only factor people consider important. > For a lot of users *predictability* is more important than absolute > performance. If my web server could run 10% faster that might be nice > but if it's capable of keeping up at its current speed it's not > terribly important. But if it means it crashes once a day because some > particular combination of parameters causes a bad plan to be used for > a specific user that's a bad trade-off. > +1 Pavel > -- > greg >