Horton
Menu

Re: Avoiding bad prepared-statement plans.

Yeb Havinga <yebhavinga@gmail.com>

View thread
From: Yeb Havinga <yebhavinga@gmail.com>
To: Bart Samwel <bart@samwel.tk>
Cc: Robert Haas <robertmhaas@gmail.com>, Jeroen Vermeulen <jtv@xs4all.nl>, pgsql-hackers@postgresql.org
Date: 2010-02-11T13:41:02Z
Lists: pgsql-hackers 
Bart Samwel wrote:
> Perhaps this could be based on a (configurable?) ratio of observed 
> planning time and projected execution time. I mean, if planning it the 
> first time took 30 ms and projected execution time is 1 ms, then by 
> all means NEVER re-plan.
IMHO looking at ms is bad for this 'possible replan' decision. The only 
comparable numbers invariant to system load are the planners costs (not 
in ms but unitless) and maybe actual number of processed tuples, but 
never actual ms.

Regards,
Yeb Havinga