* Vladimir Sitnikov (sitnikov.vladimir@gmail.com) wrote:
> 3) "suddently get slow the 6th time" is a PostgreSQL bug that both fails to
> estimate cardinality properly, and it does not provide administrator a way
> to disable the feature (generic vs specific plan).
Dropping and recreating the prepared statement is how that particular
issue is addressed.
> Query cache does have very good results for the overall web page times, and
> problems like "6th execution" are not that often.
While it may have good results in many cases, it's not accurate to say
that using prepared statements will always be faster than not.
Thanks!
Stephen
