pgsql: Fix hash aggregation to suppress unneeded columns from being - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix hash aggregation to suppress unneeded columns from being
Date
Msg-id 20060628194052.2E50B9FA425@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix hash aggregation to suppress unneeded columns from being stored in
tuple hash table entries.  This addresses the problem previously noted
that use of a 'physical tlist' in the input scan node could bloat the
hash table entries far beyond what the planner expects.  It's a better
answer than my previous thought of undoing the physical tlist optimization,
because we can also remove columns that are needed to compute the aggregate
functions but aren't part of the grouping column set.

Modified Files:
--------------
    pgsql/src/backend/executor:
        nodeAgg.c (r1.141 -> r1.142)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeAgg.c.diff?r1=1.141&r2=1.142)
    pgsql/src/include/nodes:
        execnodes.h (r1.151 -> r1.152)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/execnodes.h.diff?r1=1.151&r2=1.152)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Adjust TupleHashTables to use MinimalTuple format for contained
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Improve planner estimates for size of tuple hash tables.