Hi,
Hmm, there's only one actual question in that email, which is a
request for ideas about PL/pgsql vs. C. I suspect you didn't get any
responses because the rest of the email seems to indicate that the
patch is not very mature at this point: for example, being able to
handle updates that move rows between partitions would seem to me to
be an essential feature for a project of this type, even though there
are many practical scenarios were it's unimportant. Likewise, being
able to repartition sounds important.
With respect to the specific question about PL/pgsql vs C, I suspect
it's very unlikely that any patch of this type that relies on PL/pgsql
being loaded would be accepted into core. However, it's possible that
a useful contrib module or pgfoundry project could be spawned on that
basis, and that might be a good place to start.
I think having a useful toolkit, or a core language feature, that
supports table partitioning would be awesome and would find very broad
application... but it sounds like there is quite a bit of work left
to be done to get there.
This patch does introduce some basic syntax to help create partitions.
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.
To summarize, the community should decide if this is indeed the first step ahead.
Regards,
Nikhils
--
http://www.enterprisedb.com