Re: [PERFORMANCE] work_mem vs temp files issue - Mailing list pgsql-performance

From Robert Haas
Subject Re: [PERFORMANCE] work_mem vs temp files issue
Date
Msg-id 603c8f071001130811g22387928g72262638532370e5@mail.gmail.com
Whole thread Raw
In response to Re: [PERFORMANCE] work_mem vs temp files issue  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PERFORMANCE] work_mem vs temp files issue
List pgsql-performance
On Wed, Jan 13, 2010 at 10:42 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> I had an idea at one point of making explain show the planned and
>> actual # of batches for each hash join.  I believe that "actual # of
>> batches > 1" is isomorphic to "hash join went to disk".  The code is
>> actually pretty easy; the hard part is figuring out what to do about
>> the UI.  The choices seem to be:
>
>> 1. Create a new EXPLAIN option just for this - what would we call it?
>> 2. Think of some more, similar things and come up with a new EXPLAIN
>> option covering all of them - what else would go along with?
>> 3. Sandwhich it into an existing EXPLAIN option, most likely VERBOSE.
>> 4. Display it by default.
>
> Treat it the same as the Sort-node actual usage information.  We did not
> add a special option when we added that.

Well, what about when we're just doing EXPLAIN, not EXPLAIN ANALYZE?
It'll add another line to the output for the expected number of
batches.

...Robert

pgsql-performance by date:

Previous
From: Eduardo Piombino
Date:
Subject: Re: a heavy duty operation on an "unused" table kills my server
Next
From: Jaime Casanova
Date:
Subject: Re: [PERFORMANCE] work_mem vs temp files issue