Skip site navigation (1) Skip section navigation (2)

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

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:21:47
Message-ID: 20050123022147.53C723A4FC4@svr1.postgresql.org (view raw or flat)
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.

Modified Files:
--------------
    pgsql/src/backend/optimizer/path:
        joinpath.c (r1.91 -> r1.92)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/joinpath.c.diff?r1=1.91&r2=1.92)
        pathkeys.c (r1.63 -> r1.64)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/pathkeys.c.diff?r1=1.63&r2=1.64)
    pgsql/src/include/optimizer:
        paths.h (r1.77 -> r1.78)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/paths.h.diff?r1=1.77&r2=1.78)

pgsql-committers by date

Next:From: Tom LaneDate: 2005-01-23 02:22:43
Subject: pgsql: The result of a FULL or RIGHT join can't be assumed to be sorted
Previous:From: Bruce MomjianDate: 2005-01-23 01:01:31
Subject: Re: pgsql: Add tools/find_gt_lt to find < and > in SGML

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group