From: Guillaume Smet <guillaume.smet@gmail.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Scott Carey <scott@richrelevance.com>
Cc: bricklen <bricklen@gmail.com>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Poor plan choice in prepared statement
Date: Thu, 1 Jan 2009 19:22:56 +0100
Message-ID: <1d4e0c10901011022v4a1d5eeaidc2692a7729e79df@mail.gmail.com> (raw)
In-Reply-To: <20081231160118.GE3809@alvh.no-ip.org>
References: <33b743250812301059u31ce82faw3d72a38280b37402@mail.gmail.com>
<b42b73150812301142w4483978ahfb819b0313150dbb@mail.gmail.com>
<BDFBB77C9E07BE4A984DAAE981D19F961ACD5F388E@EXVMBX018-1.exch018.msoutlookonline.net>
<2796.1230678149@sss.pgh.pa.us>
<20081231160118.GE3809@alvh.no-ip.org>
On Wed, Dec 31, 2008 at 5:01 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> I think it has been shown enough times that the performance drop caused
> by a worse plan can be orders of magnitudes worse than what's gained by
> producing the plan only once. It does not seem a bad idea to provide a
> way to carry out only the parse phase, and postpone planning until the
> parameters have been received.
It's already done in 8.3 for unnamed plans, isn't it?
--
Guillaume
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: guillaume.smet@gmail.com, alvherre@commandprompt.com, tgl@sss.pgh.pa.us, scott@richrelevance.com, bricklen@gmail.com, scott.marlowe@gmail.com, mmoncure@gmail.com
Subject: Re: Poor plan choice in prepared statement
In-Reply-To: <1d4e0c10901011022v4a1d5eeaidc2692a7729e79df@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox