Re: [COMMITTERS] pgsql: If we expect a hash join to be performed in multiple batches,

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: If we expect a hash join to be performed in multiple batches,
Date: 2009-04-02 17:11:23
Message-ID: 1238692283.5444.123.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers


On Thu, 2009-03-26 at 17:15 +0000, Tom Lane wrote:
> Log Message:
> -----------
> If we expect a hash join to be performed in multiple batches, suppress
> "physical tlist" optimization on the outer relation (ie, force a projection
> step to occur in its scan). This avoids storing useless column values when
> the outer relation's tuples are written to temporary batch files.

Can we add "batches=N" to the EXPLAIN output for Hash and/or Hash Join?

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-04-02 17:30:53 pgsql: Fix SetClientEncoding() to maintain a cache of previously
Previous Message Bruce Momjian 2009-04-02 15:15:32 pgsql: Change psql \d* display so 'S' _or_ a pattern include system

Browse pgsql-hackers by date

  From Date Subject
Next Message Sam Mason 2009-04-02 17:35:40 Re: [HACKERS] string_to_array with empty input
Previous Message Steve Crawford 2009-04-02 16:29:04 Re: [HACKERS] string_to_array with empty input