From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: further explain changes |
Date: | 2010-01-24 21:04:35 |
Message-ID: | 603c8f071001241304n32ca3a44kc196c849113c07f8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jan 24, 2010 at 12:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)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.
Care to suggest a format?
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2010-01-24 21:12:33 | Re: default_language |
Previous Message | Simon Riggs | 2010-01-24 20:32:53 | default_language |