From: Christopher Browne <cbbrowne@acm.org>
Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres --
Date: Wed, 15 Sep 2004 02:15:08 -0400
Organization: cbbrowne Computing Inc
Lines: 19
Message-ID: <m34qm06osz.fsf@wolfe.cbbrowne.com>
References: <20040914223333.GL56059@decibel.org>
	<NOEFLCFHBPDAFHEIPGBOEEHPCEAA.simon@2ndquadrant.com>
	<60k6uw1cqa.fsf@dev6.int.libertyrms.info>
	<4147C560.9060702@joeconway.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through
 Obscurity,
	linux)
Cancel-Lock: sha1:leQavVXTFA3MVhkRH/tTHsl37po=
To: pgsql-performance@postgresql.org

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.

Sounds interesting, and possibly usable.

Where does the constraint come in that'll allow most of the data to be
excluded?

Or is this just that the entries are all part of "bigtable" so that
the self join is only 2-way?
-- 
let name="cbbrowne" and tld="acm.org" in name ^ "@" ^ tld;;
http://linuxfinances.info/info/advocacy.html
"Be humble.   A lot happened before  you were born."   - Life's Little
Instruction Book