From: Steve Atkins <steve@blighty.com>
To: pgsql-performance@postgresql.org
Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres --
Date: Wed, 15 Sep 2004 21:17:03 -0700
Message-ID: <20040916041703.GA23118@gp.word-to-the-wise.com> (raw)
In-Reply-To: <20040915111644.7cac2433@kingfisher.intern.logi-track.com>
References: <m3acvulx5f.fsf@wolfe.cbbrowne.com>
<NOEFLCFHBPDAFHEIPGBOCEFPCEAA.simon@2ndquadrant.com>
<20040914223333.GL56059@decibel.org>
<20040915051003.GA32043@gp.word-to-the-wise.com>
<20040915111644.7cac2433@kingfisher.intern.logi-track.com>
On Wed, Sep 15, 2004 at 11:16:44AM +0200, Markus Schaber wrote:
> Hi,
>
> On Tue, 14 Sep 2004 22:10:04 -0700
> Steve Atkins <steve@blighty.com> wrote:
>
> > > 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".
>
> But you have to add table constraints restricting the time after adding
> the partition?
Uhm... unless I'm confused that's not a meaningful thing in this context.
There's no rule that's putting insertions into an inherited table - the
decision of which inherited table to insert into is made at application
level.
As I was using it to segregate data based on creation timestamp the
application just inserts into the 'newest' inherited table until it's
full, then creates a new inherited table.
I've no doubt you could set up rules to scatter inserted data across
a number of tables, but that's not something that's been applicaable
for the problems I tend to work with, so I've not looked at it.
Cheers,
Steve
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: steve@blighty.com
Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres --
In-Reply-To: <20040916041703.GA23118@gp.word-to-the-wise.com>
References: <m3acvulx5f.fsf@wolfe.cbbrowne.com> <NOEFLCFHBPDAFHEIPGBOCEFPCEAA.simon@2ndquadrant.com> <20040914223333.GL56059@decibel.org> <20040915051003.GA32043@gp.word-to-the-wise.com> <20040915111644.7cac2433@kingfisher.intern.logi-track.com> <20040916041703.GA23118@gp.word-to-the-wise.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox