Hi, > > > The status has always being WIP, because what has not happened is that we > > have not had consensus on whether this is a logical first baby step ahead > > with partitioning. I haven't seen core members commenting on whether > trying > > to aggregate the current set of manual operations together via this > approach > > is worth spending further efforts, to get it into commitable shape. > > There was a lenghty, interesting discussion about this topic in the > developer meeting in Ottawa. > > http://wiki.postgresql.org/wiki/PgCon_2008_Developer_Meeting#Partitioning_Roadmap >
The discussion is indeed interesting. But again the notes do not indicate any broad consensus on the roadmap :). The current inheritance based mechanism has its pros-cons and there seem to be a multitude of requests/expectations around partitioning from different quarters. Even basic consensus about the syntax is missing. What we need is a step-by-step approach (starting with fixing up the syntax - if it can be done like that) and working our way downwards towards the underlying representation/planning for partitions... Regards, Nikhils -- http://www.enterprisedb.com
