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

From Robert Haas
Subject Re: Avoiding bad prepared-statement plans.
Date
Msg-id 603c8f071002260850r19c2c9e4gcea15621b653ae92@mail.gmail.com
Whole thread Raw
In response to Re: Avoiding bad prepared-statement plans.  (Alex Hunsaker <badalex@gmail.com>)
Responses Re: Avoiding bad prepared-statement plans.  (Alex Hunsaker <badalex@gmail.com>)
List 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


pgsql-hackers by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Hot Standby query cancellation and Streaming Replication integration
Next
From: Robert Haas
Date:
Subject: Re: Avoiding bad prepared-statement plans.