Re: Avoiding bad prepared-statement plans.

Mark Mielke <mark@mark.mielke.cc>

From: Mark Mielke <mark@mark.mielke.cc>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Jeroen Vermeulen <jtv@xs4all.nl>, Alex Hunsaker <badalex@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Greg Stark <gsstark@mit.edu>, Bart Samwel <bart@samwel.tk>, Pavel Stehule <pavel.stehule@gmail.com>, pgsql-hackers@postgresql.org

Date: 2010-02-26T19:23:22Z

Lists: pgsql-hackers

On 02/26/2010 01:59 PM, Tom Lane wrote:
> Mark Mielke<mark@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