Skip site navigation (1) Skip section navigation (2)

Re: Avoiding bad prepared-statement plans.

From: Mark Mielke <mark(at)mark(dot)mielke(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeroen Vermeulen <jtv(at)xs4all(dot)nl>, Alex Hunsaker <badalex(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Bart Samwel <bart(at)samwel(dot)tk>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Avoiding bad prepared-statement plans.
Date: 2010-02-26 19:23:22
Message-ID: 4B881FAA.9090705@mark.mielke.cc (view raw or flat)
Thread:
Lists: pgsql-hackers
On 02/26/2010 01:59 PM, Tom Lane wrote:
> Mark Mielke<mark(at)mark(dot)mielke(dot)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



In response to

pgsql-hackers by date

Next:From: Gokulakannan SomasundaramDate: 2010-02-26 19:26:11
Subject: Re: A thought on Index Organized Tables
Previous:From: Mark MielkeDate: 2010-02-26 19:22:37
Subject: Re: Avoiding bad prepared-statement plans.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group