pgsql: When dealing with multiple grouping columns coming from the same - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: When dealing with multiple grouping columns coming from the same
Date
Msg-id 20050128203431.5D0263A60AB@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
When dealing with multiple grouping columns coming from the same table,
clamp the estimated number of groups to table row count over 10, instead
of table row count; this reflects a heuristic that people probably won't
group over a near-unique set of columns, and the knowledge that we don't
currently have any way to estimate the correlation of the columns better
than guessing.  This change creates a trivial plan change in one of the
regression tests.

Modified Files:
--------------
    pgsql/src/backend/utils/adt:
        selfuncs.c (r1.169 -> r1.170)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/selfuncs.c.diff?r1=1.169&r2=1.170)
    pgsql/src/test/regress/expected:
        subselect.out (r1.10 -> r1.11)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/subselect.out.diff?r1=1.10&r2=1.11)

pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Improve planner's estimation of the space needed for HashAgg
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: When dealing with multiple grouping columns coming from the same