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

Next:	From: Fujii Masao	Date: 2010-02-10 05:05:55
	Subject: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Previous:	From: Tom Lane	Date: 2010-02-09 21:43:30
	Subject: pgsql: Fix up rickety handling of relation-truncation interlocks.