| From: | Steve Atkins <steve(at)blighty(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Data Warehouse Reevaluation - MySQL vs Postgres -- merge tables |
| Date: | 2004-09-15 05:10:04 |
| Message-ID: | 20040915051003.GA32043@gp.word-to-the-wise.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Sep 14, 2004 at 05:33:33PM -0500, Jim C. Nasby wrote:
> On Mon, Sep 13, 2004 at 11:07:35PM +0100, Simon Riggs wrote:
> > PostgreSQL's functionality is in many ways similar to Oracle Partitioning.
> >
> > Loading up your data in many similar tables, then creating a view like:
> >
> > CREATE VIEW BIGTABLE (idate, col1, col2, col3...) AS
> > SELECT 200409130800, col1, col2, col3... FROM table200409130800
> > UNION ALL
> > SELECT 200409131000, col1, col2, col3... FROM table200409131000
> > UNION ALL
> > SELECT 200409131200, col1, col2, col3... FROM table200409131200
> > ...etc...
[...]
>
> Is there by any chance a set of functions to manage adding and removing
> partitions? Certainly this can be done by hand, but having a set of
> tools would make life much easier. I just looked but didn't see anything
> on GBorg.
I've done a similar thing with time-segregated data by inheriting
all the partition tables from an (empty) parent table.
Adding a new partition is just a "create table tablefoo () inherits(bigtable)"
and removing a partition just "drop table tablefoo".
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2004-09-15 06:07:08 | Re: disk performance benchmarks |
| Previous Message | Iain | 2004-09-15 04:54:18 | Re: Data Warehouse Reevaluation - MySQL vs Postgres -- |