Vincenzo Romano wrote: > In this specific case, if you think about "inheritance for > partitioning" and you stick with the example idea of "one partition > per month", then the current solution is more than OK. > In the real world, that is not really the general case, especially in > the "enterprise grade" world, where maybe you partition with both a > time stamp and another column, like product code ranges and prefixes > ... > > Is there any planning about this improvement? Of course. People is always looking to make improvements in many areas. There are very few things that people consider to be "more than OK". The partitioning features are among those being more examined for possibly improvements. This does *not* mean that PostgreSQL doesn't serve mission critical systems already, on enterprises large and small, some of them on very large systems. What you see in these lists (people describing "partition by month" schemes) are not necessarily the most complex setups out there. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
