pgsql: The result of a FULL or RIGHT join can't be assumed to be sorted - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: The result of a FULL or RIGHT join can't be assumed to be sorted
Date
Msg-id 20050123022443.5300F3A5090@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
The result of a FULL or RIGHT join can't be assumed to be sorted by the
left input's sorting, because null rows may be inserted at various points.
Per report from Ferenc Lutisch��n.

Tags:
----
REL7_3_STABLE

Modified Files:
--------------
    pgsql/src/backend/optimizer/path:
        joinpath.c (r1.71 -> r1.71.2.1)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/joinpath.c.diff?r1=1.71&r2=1.71.2.1)
        pathkeys.c (r1.41 -> r1.41.2.1)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/pathkeys.c.diff?r1=1.41&r2=1.41.2.1)
    pgsql/src/include/optimizer:
        paths.h (r1.60 -> r1.60.2.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/paths.h.diff?r1=1.60&r2=1.60.2.1)

pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: The result of a FULL or RIGHT join can't be assumed to be sorted
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: The result of a FULL or RIGHT join can't be assumed to be sorted