Re: pgsql: Augment EXPLAIN output with more details on Hash nodes.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Augment EXPLAIN output with more details on Hash nodes.
Date: 2010-02-01 17:12:09
Message-ID: 943.1265044329@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Feb 1, 2010 at 11:53 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This needs to be damped down a bit. It should not print useless
>> non-information in cases where the plan wasn't actually run.
>> Please compare show_sort_info.

> Eh? When does it do that?

Oh, I'm sorry, it's using hashtable existence to condition the whole
output. So my complaint is backwards. I thought the intention was
to print the estimated number of batches in all cases, and then the
actual as well in EXPLAIN ANALYZE.

BTW, I think "estimated" and "actual" would be less confusing
terminology than "original".

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2010-02-01 17:28:28 Re: [COMMITTERS] pgsql: Augment EXPLAIN output with more details on Hash nodes.
Previous Message Robert Haas 2010-02-01 17:01:55 Re: pgsql: Augment EXPLAIN output with more details on Hash nodes.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-02-01 17:28:28 Re: [COMMITTERS] pgsql: Augment EXPLAIN output with more details on Hash nodes.
Previous Message Simon Riggs 2010-02-01 17:05:19 Re: Hot Standby and deadlock detection