On 02/26/2010 01:59 PM, Tom Lane wrote:
Mark Mielke<m...@mark.mielke.cc> writes:
Just to point out that I agree, and as per my original post, I think the
only time prepared statements should be re-planned for the statistics
case, is after 'analyze' has run. That sounds like a quicker solution,
and a much smaller gain. After 'analyze' of an object, invalidate all
cached plans for prepared statements that rely on that object and
require a re-plan.
Please note that that has been happening since 8.3, which is probably
why you haven't detected a problem.
Excellent, and sorry for missing the release note on this.
Thanks,
mark
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
