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

• Re: pgsql: Augment EXPLAIN output with more details on Hash nodes. at 2010-02-01 17:01:55 from Robert Haas

Responses

• Re: [COMMITTERS] pgsql: Augment EXPLAIN output with more details on Hash nodes. at 2010-02-01 17:28:28 from Robert Haas

pgsql-hackers by date

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

pgsql-committers by date

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