Re: Coster/planner and edge cases...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Loftis <mloftis(at)wgops(dot)com>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Coster/planner and edge cases...
Date: 2002-04-21 23:05:35
Message-ID: 28422.1019430335@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Loftis <mloftis(at)wgops(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 2002-04-21 23:22:40 Re: GUC vs variable.c (was Patches applied...)
Previous Message Michael Loftis 2002-04-21 22:52:23 Re: Patches applied; initdb time!