On Thu, Nov 27, 2008 at 11:09 AM, Emmanuel Cecchet <[EMAIL PROTECTED]> wrote: > I have been following that discussion very closely but it seems that we are > debating solutions without a good specification of the problem/requirements. > I would suggest that we collect all the partitioning requirements on a > dedicated Wiki page. There might not be a one size fits it all solution for > all requirements. We can also look at what other databases are proposing to > address these issues. > If we can prioritize features, that should also allow us to stage the > partitioning implementation.
This might be a good idea. Want to take a crack at it? > I have a prototype insert trigger in C that directly move inserts in a > master table to the appropriate child table (directly moving the tuple). Let > me know if anyone is interested. Can't hurt to post it. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
