From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Christopher Browne <cbbrowne(at)acm(dot)org> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Data Warehouse Reevaluation - MySQL vs Postgres -- |
Date: | 2004-09-16 05:17:45 |
Message-ID: | 414921F9.400@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Christopher Browne wrote:
> In the last exciting episode, mail(at)joeconway(dot)com (Joe Conway) wrote:
>>That's exactly what we're doing, but using inherited tables instead of
>>a union view. With inheritance, there is no need to rebuild the view
>>each time a table is added or removed. Basically, in our application,
>>tables are partitioned by either month or week, depending on the type
>>of data involved, and queries are normally date qualified.
> Where does the constraint come in that'll allow most of the data to be
> excluded?
Not sure I follow this.
> Or is this just that the entries are all part of "bigtable" so that
> the self join is only 2-way?
We don't have a need for self-joins in our application. We do use a
crosstab function to materialize some transposed views of the data,
however. That allows us to avoid self-joins in the cases where we might
otherwise need them.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Clery | 2004-09-16 07:41:37 | Comparing user attributes with bitwise operators |
Previous Message | Iain | 2004-09-16 05:08:34 | Re: Data Warehouse Reevaluation - MySQL vs Postgres -- |