Message-Id: <1168524121.14614.1168744439@webmail.messagingengine.com>
From: "Jeremy Haile" <jhaile@fastmail.fm>
To: pgsql-performance@postgresql.org
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ISO-8859-1"
MIME-Version: 1.0
References: <7F10D26ECFA1FB458B89C5B4B0D72C2B82CD0A@sesrv12.wirelesscar.com>
	<20070110202006.GU12217@nasby.net> <45A54CF5.3090103@myemma.com>
	<7F10D26ECFA1FB458B89C5B4B0D72C2B82CFCF@sesrv12.wirelesscar.com>
Subject: Re: Partitioning
In-Reply-To: <7F10D26ECFA1FB458B89C5B4B0D72C2B82CFCF@sesrv12.wirelesscar.com>
Date: Thu, 11 Jan 2007 09:02:01 -0500

Well - whether or not MySQL's implementation of partitioning has some
deficiency, it sure is a lot easier to set up than PostgreSQL.  And I
don't think there is any technical reason that setting up partitioning
on Postgres couldn't be very easy and still be robust.

On Thu, 11 Jan 2007 13:59:20 +0100, "Mikael Carneholm"
<Mikael.Carneholm@WirelessCar.com> said:
> > On Fri, Jan 05, 2007 at 12:47:08PM +0100, Mikael Carneholm wrote:
> > >> Take a look at the set of partitioning functions I wrote shortly
> after
> > >> the 8.1 release:
> > >>
> > >> http://www.studenter.hb.se/~arch/files/part_functions.sql
> > >>
> > >> You could probably work something out using those functions (as-is,
> or
> > >> as inspiration) together with pgAgent
> > >> (http://www.pgadmin.org/docs/1.4/pgagent.html)
> > >>
> > >> /Mikael
> > >>
> > Those are  some great functions.
> > 
> 
> Well, they're less than optimal in one aspect: they add one rule per
> partition, making them unsuitable for OLTP type applications (actually:
> any application where insert performance is crucial). Someone with time
> and/or energy could probably fix that, I guess...patches are welcome :)
> 
> /Mikael
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings