Re: Data Warehouse Reevaluation - MySQL vs Postgres -- - Mailing list pgsql-performance

From Joe Conway
Subject Re: Data Warehouse Reevaluation - MySQL vs Postgres --
Date
Msg-id 414921F9.400@joeconway.com
Whole thread Raw
In response to Re: Data Warehouse Reevaluation - MySQL vs Postgres --  (Christopher Browne <cbbrowne@acm.org>)
List pgsql-performance
Christopher Browne wrote:
> In the last exciting episode, mail@joeconway.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

pgsql-performance by date:

Previous
From: "Iain"
Date:
Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres --
Next
From: Kevin Neufeld
Date:
Subject: declared cursor uses slow plan