Robert Haas writes:
> On Mon, Feb 1, 2010 at 11:53 AM, Tom Lane 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 has
On Mon, Feb 1, 2010 at 11:53 AM, Tom Lane wrote:
> rh...@postgresql.org (Robert Haas) writes:
>> Log Message:
>> ---
>> Augment EXPLAIN output with more details on Hash nodes.
>
> This needs to be damped down a bit. It should not print useless
> non-information in cases where the plan was
rh...@postgresql.org (Robert Haas) writes:
> Log Message:
> ---
> Augment EXPLAIN output with more details on Hash nodes.
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.
Log Message:
---
Augment EXPLAIN output with more details on Hash nodes.
We show the number of buckets, the number of batches (and also the original
number if it has changed), and the peak space used by the hash table. Minor
executor changes to track peak space used.
Modified Files:
