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 20050123022243.AB7CE3A507F@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:
----
REL8_0_STABLE

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

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/joinpath.c.diff?r1=1.91&r2=1.91.4.1)
        pathkeys.c (r1.63 -> r1.63.4.1)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/pathkeys.c.diff?r1=1.63&r2=1.63.4.1)
    pgsql/src/include/optimizer:
        paths.h (r1.77 -> r1.77.4.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/paths.h.diff?r1=1.77&r2=1.77.4.1)

pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pgsql: Add tools/find_gt_lt to find < and > in SGML
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