On Sun, Jan 16, 2005 at 04:08:35PM -0500, Tom Lane wrote: > Michael Fuhr <[EMAIL PROTECTED]> writes: > > > Is taking the downside into consideration a tough problem to solve, or > > is it simply not worthwhile in the large? > > I don't know how to solve it, and whether it would be worthwhile would > depend considerably on how expensive the proposed solution is ...
Would the topic merit discussion in pgsql-hackers after the dust from the 8.0 release settles down? I know little of the theory behind query planning; I'd hate to waste the developers' time on a topic that's already been debated or that has little merit. If the topic is worthwhile, then I was thinking of a configuration setting that would allow the user to request either "the plan most likely to be the fastest" or "the plan least likely to be the slowest," or maybe something in between. -- Michael Fuhr http://www.fuhr.org/~mfuhr/ ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
