Re: Avoiding bad prepared-statement plans.
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Alex Hunsaker <badalex@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Jeroen Vermeulen <jtv@xs4all.nl>, Greg Stark <gsstark@mit.edu>, Bart Samwel <bart@samwel.tk>, Pavel Stehule <pavel.stehule@gmail.com>, pgsql-hackers@postgresql.org
Date: 2010-02-26T16:50:37Z
Lists: pgsql-hackers
On Fri, Feb 26, 2010 at 1:29 AM, Alex Hunsaker <badalex@gmail.com> wrote: > Prepared plans + exec plan (new guc/ protocol thing): > Use: not quite sure > Problems: slow because it would replan every time > Solutions: use a prepared plan with the appropriate things not > parametrized...? > > [ aka we already have this, its called dont use a prepared statement ] The point is sometimes you'd like to replan every time, but not reparse every time. There's no way to do that ATM. ...Robert