X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6B65E329D55 for ; Thu, 16 Sep 2004 05:09:47 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 19324-08 for ; Thu, 16 Sep 2004 04:09:42 +0000 (GMT) Received: from gp.word-to-the-wise.com (gp.word-to-the-wise.com [64.71.176.18]) by svr1.postgresql.org (Postfix) with ESMTP id 5E9D5329D68 for ; Thu, 16 Sep 2004 05:09:41 +0100 (BST) Received: by gp.word-to-the-wise.com (Postfix, from userid 500) id 293479029F2; Wed, 15 Sep 2004 21:17:03 -0700 (PDT) Date: Wed, 15 Sep 2004 21:17:03 -0700 From: Steve Atkins To: pgsql-performance@postgresql.org Subject: Re: Data Warehouse Reevaluation - MySQL vs Postgres -- Message-ID: <20040916041703.GA23118@gp.word-to-the-wise.com> References: <20040914223333.GL56059@decibel.org> <20040915051003.GA32043@gp.word-to-the-wise.com> <20040915111644.7cac2433@kingfisher.intern.logi-track.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040915111644.7cac2433@kingfisher.intern.logi-track.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/150 X-Sequence-Number: 8278 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 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