From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Use a hopefully-more-reliable method of detecting default |
Date: | 2004-11-09 00:34:51 |
Message-ID: | 20041109003451.A4C4F3A413F@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
Use a hopefully-more-reliable method of detecting default selectivity
estimates when combining the estimates for a range query. As pointed out
by Miquel van Smoorenburg, the existing check for an impossible combined
result would quite possibly fail to detect one default and one non-default
input. It seems better to use the default range query estimate in such
cases. To do so, add a check for an estimate of exactly DEFAULT_INEQ_SEL.
This is a bit ugly because it introduces additional coupling between
clauselist_selectivity and scalarltsel/scalargtsel, but it's not like
there wasn't plenty already...
Modified Files:
--------------
pgsql/src/backend/optimizer/path:
clausesel.c (r1.70 -> r1.71)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/clausesel.c.diff?r1=1.70&r2=1.71)
pgsql/src/backend/utils/adt:
selfuncs.c (r1.166 -> r1.167)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/selfuncs.c.diff?r1=1.166&r2=1.167)
pgsql/src/include/utils:
selfuncs.h (r1.19 -> r1.20)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/selfuncs.h.diff?r1=1.19&r2=1.20)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-11-09 03:02:51 | pgsql: Remove inheritance, already in TODO. |
Previous Message | Bruce Momjian | 2004-11-08 20:16:47 | pgsql: Remove fadvise TODO.detail. |