| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alex Hunsaker <badalex(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeroen Vermeulen <jtv(at)xs4all(dot)nl>, 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 16:50:37 |
| Message-ID: | 603c8f071002260850r19c2c9e4gcea15621b653ae92@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 26, 2010 at 1:29 AM, Alex Hunsaker <badalex(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-02-26 16:51:53 | Re: Avoiding bad prepared-statement plans. |
| Previous Message | Richard Huxton | 2010-02-26 16:43:24 | Re: Hot Standby query cancellation and Streaming Replication integration |