| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Prepared statements considered harmful |
| Date: | 2006-08-31 19:14:32 |
| Message-ID: | 20060831191432.GL27851@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 31, 2006 at 02:58:48PM -0400, Tom Lane wrote:
> The protocol does let you use OOL parameters without retaining a
> prepared plan, thanks to the hack introduced later to not plan the
> unnamed statement at Parse time, but that's definitely a bit of a wart
> on the original protocol design. Maybe it's good enough, or maybe not.
Urk, so it was a hack. Unfortunatly it seems something you can't really
change without changing the protocol.
So what are the options now? A GUC like so:
prepare_means_plan = [true|false]
So then a prepare will always parse straightaway, but you can choose
whether or not you want to plan straightaway or at bind time.
Would this be acceptable?
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2006-08-31 19:17:38 | Re: Prepared statements considered harmful |
| Previous Message | Joshua D. Drake | 2006-08-31 19:14:25 | Re: Thought provoking piece on NetBSD |