| From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix oversight in 8.0 modification of RestrictInfo data |
| Date: | 2005-10-11 16:45:01 |
| Message-ID: | 20051011164501.2FAB1D6FDF@svr1.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Fix oversight in 8.0 modification of RestrictInfo data structures.
A RestrictInfo representing an OR clause now contains two versions of
the contained expression, one with sub-RestrictInfos and one without.
clause_selectivity() should descend to the version with sub-RestrictInfos
so that it has a chance of caching its results for the OR's sub-clauses.
Failing to do so resulted in redundant planner effort.
Tags:
----
REL8_0_STABLE
Modified Files:
--------------
pgsql/src/backend/optimizer/path:
clausesel.c (r1.72 -> r1.72.4.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/clausesel.c.diff?r1=1.72&r2=1.72.4.1)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-10-11 17:27:14 | pgsql: Document that get_attstatsslot/free_attstatsslot only need to be |
| Previous Message | Tom Lane | 2005-10-11 16:44:40 | pgsql: Fix oversight in 8.0 modification of RestrictInfo data |