diff options
author | Bruce Momjian | 2005-12-17 19:03:24 +0000 |
---|---|---|
committer | Bruce Momjian | 2005-12-17 19:03:24 +0000 |
commit | 25af534ea134cff88342e5e270e6a213a1b7edb4 (patch) | |
tree | 61af2c05ee12567d9634ab1ae2becb95a0193036 | |
parent | 3282b6338b6ae3303c36aae213ee6d8686419421 (diff) |
Remove item:
< * Allow star join optimizations
<
< While our bitmap scan allows multiple indexes to be joined to get
< to heap rows, a star joins allows multiple dimension _tables_ to
< be joined to index into a larger main fact table. The join is
< usually performed by either creating a cartesian product of all
< the dimmension tables and doing a single join on that product or
< using subselects to create bitmaps of each dimmension table match
< and merge the bitmaps to perform the join on the fact table. Some
< of these algorithms might be patented.
-rw-r--r-- | doc/TODO | 12 | ||||
-rw-r--r-- | doc/src/FAQ/TODO.html | 12 |
2 files changed, 2 insertions, 22 deletions
@@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) -Last updated: Sat Dec 17 13:06:57 EST 2005 +Last updated: Sat Dec 17 14:03:20 EST 2005 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -1029,16 +1029,6 @@ Optimizer / Executor * Log statements where the optimizer row estimates were dramatically different from the number of rows actually found? -* Allow star join optimizations - - While our bitmap scan allows multiple indexes to be joined to get - to heap rows, a star joins allows multiple dimension _tables_ to - be joined to index into a larger main fact table. The join is - usually performed by either creating a cartesian product of all - the dimmension tables and doing a single join on that product or - using subselects to create bitmaps of each dimmension table match - and merge the bitmaps to perform the join on the fact table. Some - of these algorithms might be patented. Miscellaneous Performance diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 80247626b51..32add687d56 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@ <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <h1><a name="section_1">PostgreSQL TODO List</a></h1> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/> -Last updated: Sat Dec 17 13:06:57 EST 2005 +Last updated: Sat Dec 17 14:03:20 EST 2005 </p> <p>The most recent version of this document can be viewed at<br/> <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. @@ -934,16 +934,6 @@ first. </p> </li><li>Log statements where the optimizer row estimates were dramatically different from the number of rows actually found? - </li><li>Allow star join optimizations -<p> While our bitmap scan allows multiple indexes to be joined to get - to heap rows, a star joins allows multiple dimension _tables_ to - be joined to index into a larger main fact table. The join is - usually performed by either creating a cartesian product of all - the dimmension tables and doing a single join on that product or - using subselects to create bitmaps of each dimmension table match - and merge the bitmaps to perform the join on the fact table. Some - of these algorithms might be patented. -</p> </li></ul> <h1><a name="section_21">Miscellaneous Performance</a></h1> |