2 ms·
The partitioning features in PG10 and PG11 were also supported by said extensions, but now they're batteries-included features. The GP is implying that, as long
by derefr 9y ago
The partitioning features in PG10 and PG11 were also supported by said extensions, but now they're batteries-included features. The GP is implying that, as long as they're eating the lunch of these extensions, they should eat the whole lunch.
(Which I personally agree with, given that you almost never get these extension—or support for arbitrary extensions—on Postgres DBaaS hosts. Upstreaming a feature = making it available on these hosts.)
- tpetry 9y agoThe development model of postgres is to start with a simply le implementation and improve it with every release. So maybe with pg13 or 14 this will be available in the core if one developer starts working on the remaining features.
- arghwhat 9y agoThere is a very sharp distinction between providing first-class partitioning, and providing automated maintenance and performance tuning. Providing first-class partitioning is something that extensions can't possibly provide, due to how many places this has to integrate with. On the other hand, manipulating partitions (which is effectively automatic table creation) seems like the sort of magic I expect to only exist in extensions. As mentioned in a different comment, it does sound like people are looking for round-robin load distribution rather than partitioning.