+1 to seamless partitioning. Although the idea of having a student work on this seems a bit scary, but what seems scary to me may be a piece of cake for a talented kid :-) Kiriakos http://www.mockbites.com On Mar 13, 2012, at 3:07 PM, John R Pierce wrote: > On 03/08/12 12:01 PM, Andy Colson wrote: >> >> 2) better partitioning support. Something much more automatic. > > that would be really high on our list. and something that can handle adding/dropping partitions while there's concurrent transactions involving the partitioned table > > also a planner that can cope with optimizing prepared statements where the partitioning variable is a passed parameter. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
