From: | "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Phil Frost" <indigo(at)bitglue(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Prepared statements considered harmful |
Date: | 2006-09-01 15:26:07 |
Message-ID: | 23335.125.24.240.23.1157124367.squirrel@webmail.xs4all.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, September 1, 2006 21:30, Tom Lane wrote:
> Yeah. One of the reasons the planner is acceptably fast is that it is
> aggressive about discarding candidate plans as soon as they are clearly
> inferior to other plans. Tracking multiple plans that might be optimal
> under varying assumptions about the query parameters would make things
> exponentially slower.
AFAICS the planner shouldn't be affected at all--it'd just be invoked more
often as and when the need for new plans became apparent. Not
"exponentially" (that's an overused word anyway) but "proportionally" to
that.
I've been assuming that once you have a plan, storing it is not very
expensive. If, say, doubling the number of plans stored with a session's
prepared statements incurs some serious cost (apart from the planning
itself, of course) then that changes things.
Jeroen
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-09-01 15:26:44 | Re: Prepared statements considered harmful |
Previous Message | Gregory Stark | 2006-09-01 15:14:32 | Re: Prepared statements considered harmful |