pgsql: Do not allow Unique nodes to be scanned backwards. - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Do not allow Unique nodes to be scanned backwards.
Date
Msg-id 20080805212842.C37E2755315@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Do not allow Unique nodes to be scanned backwards.  The code claimed that it
would work, but in fact it didn't return the same rows when moving backwards
as when moving forwards.  This would have no visible effect in a DISTINCT
query (at least assuming the column datatypes use a strong definition of
equality), but it gave entirely wrong answers for DISTINCT ON queries.

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
    pgsql/src/backend/executor:
        execAmi.c (r1.89.2.2 -> r1.89.2.3)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execAmi.c?r1=1.89.2.2&r2=1.89.2.3)
        nodeUnique.c (r1.53 -> r1.53.2.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeUnique.c?r1=1.53&r2=1.53.2.1)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Do not allow Unique nodes to be scanned backwards.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Do not allow Unique nodes to be scanned backwards.