Re: Avoiding bad prepared-statement plans. - Mailing list pgsql-hackers

From Mark Mielke
Subject Re: Avoiding bad prepared-statement plans.
Date
Msg-id 4B881FAA.9090705@mark.mielke.cc
Whole thread Raw
In response to Re: Avoiding bad prepared-statement plans.  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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




pgsql-hackers by date:

Previous
From: Mark Mielke
Date:
Subject: Re: Avoiding bad prepared-statement plans.
Next
From: Gokulakannan Somasundaram
Date:
Subject: Re: A thought on Index Organized Tables