From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: The result of a FULL or RIGHT join can't be assumed to be sorted |
Date: | 2005-01-23 02:23:39 |
Message-ID: | 20050123022339.483453A50C0@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 Lutischn.
Tags:
----
REL7_4_STABLE
Modified Files:
--------------
pgsql/src/backend/optimizer/path:
joinpath.c (r1.82.2.1 -> r1.82.2.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/joinpath.c.diff?r1=1.82.2.1&r2=1.82.2.2)
pathkeys.c (r1.53.4.1 -> r1.53.4.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/pathkeys.c.diff?r1=1.53.4.1&r2=1.53.4.2)
pgsql/src/include/optimizer:
paths.h (r1.69 -> r1.69.4.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/paths.h.diff?r1=1.69&r2=1.69.4.1)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-01-23 02:24:43 | pgsql: The result of a FULL or RIGHT join can't be assumed to be sorted |
Previous Message | Tom Lane | 2005-01-23 02:22:43 | pgsql: The result of a FULL or RIGHT join can't be assumed to be sorted |