Tom Lane wrote:
> Michael Loftis <[EMAIL PROTECTED]> writes:
> > IE I'd like to have the information come back as say a notice or maybe
> > as extra information for an EXPLAIN for my purposes, but unless there is
> > interest, consensus on how it should be done, and a TODO item made of
> > it, I won't be making a patch of that, no reason to clutter the backend
> > with stuff that hopefully won't be needed for long :)
>
> I think it'd be useful to have, actually, as long as we're not talking
> about much code bloat. I tend to try to find a way to see what I want
> with EXPLAIN, because using OPTIMIZER_DEBUG is such a pain. But it's
> often difficult to force the plan I'm interested in to rise to the top.
> A nicer user interface for looking at the rejected alternatives would
> seem like a step forward to me, whether or not ordinary users have any
> need for it...
I think there is consensus. Added to TODO:
Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
