On Mon, Jun 20, 2011 at 5:42 PM, David Fetter <da...@fetter.org> wrote: > I noticed that we have some nice new speed optimizations (more > properly, de-pessimizations) for partitioned tables in 9.1.
/me sticks tongue out at dfetter. > Anybody care to look over the table partitioning stuff on the wiki and > check it for relevance? > > http://wiki.postgresql.org/wiki/Table_partitioning Itagaki Takahiro had a patch for this about a year ago, but I wasn't happy with the system catalog representation he chose and I think there were some other issues as well. Still, I think a pretty clear way forward here is to try to figure out a way to add some explicit syntax for range partitions, so that you can say... foo_a is for all rows where foo starts with 'a' foo_b is for all rows where foo starts with 'b' ... foo_xyz is for all rows where foo starts with 'xyz' If we have that data represented explicitly in the system catalog, then we can look at doing built-in INSERT-routing and UPDATE-handling. For an added bonus, it's a more natural syntax. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
