From: | tgl(at)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Temporarily (I hope) disable flattening of IN/EXISTS sublinks |
Date: | 2009-02-27 23:30:29 |
Message-ID: | 20090227233029.B331E7559ED@cvs.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Log Message:
-----------
Temporarily (I hope) disable flattening of IN/EXISTS sublinks that are within
the ON clause of an outer join. Doing so is semantically correct but results
in de-optimizing queries that were structured to take advantage of the sublink
style of execution, as seen in recent complaint from Kevin Grittner. Since
the user can get the other behavior by reorganizing his query, having the
flattening happen automatically is just a convenience, and that doesn't
justify breaking existing applications. Eventually it would be nice to
re-enable this, but that seems to require a significantly different approach
to outer joins in the executor.
Modified Files:
--------------
pgsql/src/backend/optimizer/prep:
prepjointree.c (r1.63 -> r1.64)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/prep/prepjointree.c?r1=1.63&r2=1.64)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-02-28 00:10:52 | pgsql: Reduce the maximum value of vacuum_cost_delay and |
Previous Message | Tom Lane | 2009-02-27 22:41:38 | pgsql: Tighten up join ordering rules to account for recent more-careful |
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2009-02-27 23:37:51 | Re: xpath processing brain dead |
Previous Message | Jeff Davis | 2009-02-27 23:01:14 | Re: Index correlation versus multi-column indexes |