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

From Tom Lane
Subject Re: Avoiding bad prepared-statement plans.
Date
Msg-id 3138.1267214276@sss.pgh.pa.us
Whole thread Raw
In response to Re: Avoiding bad prepared-statement plans.  (Mark Mielke <mark@mark.mielke.cc>)
Responses Re: Avoiding bad prepared-statement plans.  (Mark Mielke <mark@mark.mielke.cc>)
List pgsql-hackers
Mark Mielke <mark@mark.mielke.cc> writes:
> There must be some way to lift the cost of planning out of the plan 
> enumeration and selection phase, such that only plan enumeration and 
> selection is run at execute time. In most cases, plan enumeration and 
> selection, provided that all data required to make these decisions is 
> all cached in data structures ready to go, should be very fast? Right? 

Huh?  What exactly do you think the cost of planning is, if not
enumeration and selection?  There isn't very much that's cacheable,
at least not in any sanely-sized cache.

> By "not worth it", do you mean development effort or run time?

Run time.  The development cost of what you are proposing is negligible:
just rip out the plan cache altogether.  I don't believe it would be a
performance win though.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Gokulakannan Somasundaram
Date:
Subject: Re: A thought on Index Organized Tables
Next
From: Greg Stark
Date:
Subject: Re: A thought on Index Organized Tables