From: | Olgierd Michalak <olgierdm(at)softcomputer(dot)com> |
---|---|
To: | "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org> |
Subject: | How to implement Aggregate Awareness? |
Date: | 2011-11-04 20:09:03 |
Message-ID: | F8991549C624E2429C578E86D68A4D027F42A970@EXCH-MBX01.softcomputer.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
I wonder how to implement Aggregate Awareness or Transparent Aggregate Navigation in PostgreSQL?
Simply put, when Transparent (to the reporting tool) Aggregate Navigator recognizes that a query would execute faster using aggregates, it automatically rewrites the query so that the database hits the smaller aggregates rather than larger detail tables upon which the small aggregates are pre-computed. The simple theory for BI/DWH was set out by Ralph Kimball (http://www.kimballgroup.com/html/articles_search/articles1996/9608d54.html) Some tools, including Oracle, provide such functionality, and I wonder if it is possible to implement such Aggregate Awareness in PostgreSQL.
Re-write rules in PostgreSQL come to mind first. After a few attempts, I realized that they may not be sophisticated enough to provide a viable solution. But perhaps they are, or there are other features in PostgreSQL that would allow for such aggregate awareness. If you have good ideas about how to implement this functionality, please respond.
Thank you,
Olgierd Michalak
Soft Computer Consultants, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Olgierd Michalak | 2011-11-04 21:03:47 | How to implement Aggregate Awareness? |
Previous Message | Richard Huxton | 2011-11-04 18:06:37 | Re: the use of $$string$$ |