Re: Coster/planner and edge cases... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Coster/planner and edge cases...
Date
Msg-id 28422.1019430335@sss.pgh.pa.us
Whole thread Raw
In response to Re: Coster/planner and edge cases...  (Michael Loftis <mloftis@wgops.com>)
Responses Re: Coster/planner and edge cases...  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Michael Loftis <mloftis@wgops.com> 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...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Michael Loftis
Date:
Subject: Re: Patches applied; initdb time!
Next
From: Thomas Lockhart
Date:
Subject: Re: GUC vs variable.c (was Patches applied...)