Re: further explain changes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: further explain changes
Date
Msg-id 27825.1264354226@sss.pgh.pa.us
Whole thread Raw
In response to Re: further explain changes  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: further explain changes
Re: further explain changes
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Sun, Jan 24, 2010 at 12:06 AM, Jaime Casanova
>> why not let it go in ANALYZE, just as the sort info

> It's kinda long-winded - it adds like 4 extra lines for each hash
> join.  I don't think I want to add that much clutter to regular E-A
> output.

Well, that would only happen if you're deliberately obtuse about the
formatting.  The sort code manages to fit all the extra on one line,
and I don't see why hash couldn't.

I'd vote for just adding it in the exact same cases that sort adds extra
info.  -1 for either adding a new option or changing the meaning of the
ones that are there.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: tab completion for prepared transactions?
Next
From: Bruce Momjian
Date:
Subject: Re: tab completion for prepared transactions?