pgsql-server/src backend/commands/explain.c ba ... - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql-server/src backend/commands/explain.c ba ...
Date
Msg-id 20021106000045.1D292475B47@postgresql.org
Whole thread Raw
List pgsql-committers
CVSROOT:    /cvsroot
Module name:    pgsql-server
Changes by:    tgl@postgresql.org    02/11/05 19:00:45

Modified files:
    src/backend/commands: explain.c
    src/backend/executor: nodeAgg.c nodeGroup.c
    src/backend/nodes: copyfuncs.c equalfuncs.c outfuncs.c
                       readfuncs.c
    src/backend/optimizer: README
    src/backend/optimizer/geqo: geqo_misc.c
    src/backend/optimizer/path: allpaths.c
    src/backend/optimizer/plan: createplan.c planmain.c planner.c
    src/backend/optimizer/util: pathnode.c
    src/include/nodes: execnodes.h nodes.h parsenodes.h plannodes.h
                       relation.h
    src/include/optimizer: geqo_misc.h pathnode.h planmain.h

Log message:
    First phase of implementing hash-based grouping/aggregation.  An AGG plan
    node now does its own grouping of the input rows, and has no need for a
    preceding GROUP node in the plan pipeline.  This allows elimination of
    the misnamed tuplePerGroup option for GROUP, and actually saves more code
    in nodeGroup.c than it costs in nodeAgg.c, as well as being presumably
    faster.  Restructure the API of query_planner so that we do not commit to
    using a sorted or unsorted plan in query_planner; instead grouping_planner
    makes the decision.  (Right now it isn't any smarter than query_planner
    was, but that will change as soon as it has the option to select a hash-
    based aggregation step.)  Despite all the hackery, no initdb needed since
    only in-memory node types changed.


pgsql-committers by date:

Previous
From: petere@postgresql.org (Peter Eisentraut - PostgreSQL)
Date:
Subject: pgsql-server/src backend/po/Tag: backend/po/RE ...
Next
From: momjian@postgresql.org (Bruce Momjian - CVS)
Date:
Subject: pgsql-server/doc TODO