RE: How to make partitioning scale better for larger numbers ofpartitions
От | Tsunakawa, Takayuki |
---|---|
Тема | RE: How to make partitioning scale better for larger numbers ofpartitions |
Дата | |
Msg-id | 0A3221C70F24FB45833433255569204D1FA5002F@G01JPEXMBYT05 обсуждение исходный текст |
Ответ на | Re: How to make partitioning scale better for larger numbers of partitions (David Rowley <david.rowley@2ndquadrant.com>) |
Ответы |
Re: How to make partitioning scale better for larger numbers of partitions
|
Список | pgsql-hackers |
From: David Rowley [mailto:david.rowley@2ndquadrant.com] > > David has submitted multiple patches for PG 12, one of which speeds up > pruning of UPDATE/DELETE (I couldn't find it in the current CF, though.) > What challenges are there for future versions, and which of them are being > addressed by patches in progress for PG 12, and which issues are untouched? > > I've not submitted that for PG12 yet. I had other ideas about just > getting rid of the inheritance planner altogether, but so far don't > have a patch for that. Still uncertain if there are any huge blockers > to that either. Sorry, I seem to have misunderstood something. By the way, what do you think is the "ideal and should-be-feasible" goal and the "realistic" goal we can reach in the nearfuture (e.g. PG 12)? Say, * Planning and execution time is O(log n), where n is the number of partitions * Planning time is O(log n), execution time is O(1) * Planning and execution time is O(1), where n is the number of partitions Regards Takayuki Tsunakawa
В списке pgsql-hackers по дате отправления: