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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
