BTW, someone coming up with a set of functions to handle partitioning for the general 'partition by time' case would make a GREAT project on pgFoundry. 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 > > > -----Original Message----- > > From: pgsql-performance-owner@xxxxxxxxxxxxxx > [mailto:pgsql-performance- > > owner@xxxxxxxxxxxxxx] On Behalf Of Arnau > > Sent: den 5 januari 2007 12:02 > > To: pgsql-performance@xxxxxxxxxxxxxx > > Subject: [PERFORM] Partitioning > > > > Hi all, > > > > I'm not sure if this question fits in the topic of this list. > > > > I'm interested in partitioning and it's the first time I'd use it. > > There is an issue I don't know how you handle it. Lets say I'm > > interested in store monthly based statistical data like the example of > > http://www.postgresql.org/docs/8.2/static/ddl-partitioning.html. What > I > > don't like of this approach is that the monthly tables, rules... must > be > > created "manually" or at least I haven't found any other option. > > > > My question is how do you manage this? do you have a cron task that > > creates automatically these monthly elements (tables, rules, ... ) or > > there is another approach that doesn't require external things like > cron > > only PostgreSQL. > > -- > > Arnau > > > > ---------------------------(end of > broadcast)--------------------------- > > TIP 5: don't forget to increase your free space map settings > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > -- Jim Nasby jim@xxxxxxxxx EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
