pgsql: Improve planner's choices about when to use hashing vs sorting - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Improve planner's choices about when to use hashing vs sorting
Date
Msg-id 20100210033835.8C4A57541B9@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Improve planner's choices about when to use hashing vs sorting for DISTINCT.

The previous coding missed a bet by sometimes picking the "sorted" path
from query_planner even though hashing would be preferable.  To fix, we have
to be willing to make the choice sooner.  This contorts things a little bit,
but I thought of a factorization that makes it not too awful.

Modified Files:
--------------
    pgsql/src/backend/optimizer/plan:
        planner.c (r1.263 -> r1.264)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planner.c?r1=1.263&r2=1.264)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix up rickety handling of relation-truncation interlocks.
Next
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Now that streaming replication switches between streaming mode