Message-ID: <508E83BB.4060101@optionshouse.com>
Date: Mon, 29 Oct 2012 08:25:15 -0500
From: Shaun Thomas <sthomas@optionshouse.com>
Reply-To: <sthomas@optionshouse.com>
Organization: Peak6
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Daniel Burbridge <Daniel.Burbridge@publishingtechnology.com>,
	"pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Prepared statements slow in 9.2 still (bad query plan)
References: <CA9A03D82318FE41825E250D9880D959B3BFD5@maple.VISTACOMP.COM>
	<12200.1351436781@sss.pgh.pa.us>
In-Reply-To: <12200.1351436781@sss.pgh.pa.us>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
content-transfer-encoding: 7bit

On 10/28/2012 10:06 AM, Tom Lane wrote:

> 9.2 will only pick the "right" plan if that plan's estimated cost is a
> good bit cheaper than the "wrong" parameterized plan.

Is it also possible that the planner differences between extended and 
simple query mode caused this? That really bit us in the ass until 
EnterpriseDB sent us a patch. From browsing the threads, didn't someone 
say a similar problem existed in PG core?

-- 
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas@optionshouse.com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email