pgsql: Avoid considering both sort directions as equally useful for - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Avoid considering both sort directions as equally useful for
Date
Msg-id 20071027054543.A0EC0754229@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Avoid considering both sort directions as equally useful for merging.
This doubles the planning workload for mergejoins while not actually
accomplishing much.  The only useful case is where one of the directions
matches the query's ORDER BY request; therefore, put a thumb on the scales
in that direction, and otherwise arbitrarily consider only the ASC direction.
(This is a lot easier now than it would've been before 8.3, since we have
more semantic knowledge embedded in PathKeys now.)

Modified Files:
--------------
    pgsql/src/backend/optimizer/path:
        pathkeys.c (r1.85 -> r1.86)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/pathkeys.c?r1=1.85&r2=1.86)

pgsql-committers by date:

Previous
From: hinoue@pgfoundry.org (User Hinoue)
Date:
Subject: psqlodbc - psqlodbc: The version is now 8.2.0501.
Next
From: Simon Riggs
Date:
Subject: Re: pgsql: Allow an autovacuum worker to be interrupted automatically when