pgsql: Tighten up join ordering rules to account for recent more-careful

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Tighten up join ordering rules to account for recent more-careful
Date: 2009-02-27 22:41:38
Message-ID: 20090227224138.17FAC7559ED@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Tighten up join ordering rules to account for recent more-careful analysis
of the associativity of antijoins. Also improve optimizer/README discussion
of outer join ordering rules.

Modified Files:
--------------
pgsql/src/backend/optimizer:
README (r1.48 -> r1.49)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/README?r1=1.48&r2=1.49)
pgsql/src/backend/optimizer/path:
joinrels.c (r1.98 -> r1.99)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/joinrels.c?r1=1.98&r2=1.99)
pgsql/src/backend/optimizer/plan:
initsplan.c (r1.148 -> r1.149)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/initsplan.c?r1=1.148&r2=1.149)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-02-27 23:30:29 pgsql: Temporarily (I hope) disable flattening of IN/EXISTS sublinks
Previous Message Heikki Linnakangas 2009-02-27 16:35:53 pgsql: In CREATE CONVERSION, test that the given function is a valid