Re: Speeding up INSERTs and UPDATEs to partitioned tables
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Speeding up INSERTs and UPDATEs to partitioned tables |
| Дата | |
| Msg-id | 20181114181050.6l3lgrxg5bterpkh@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: Speeding up INSERTs and UPDATEs to partitioned tables (David Rowley <david.rowley@2ndquadrant.com>) |
| Ответы |
Re: Speeding up INSERTs and UPDATEs to partitioned tables
|
| Список | pgsql-hackers |
What's with this comment?
* Initially we must only set up 1 PartitionDispatch object; the one for
* the partitioned table that's the target of the command. If we must
* route a tuple via some sub-partitioned table, then its
* PartitionDispatch is only built the first time it's required.
You're setting the allocsize to PARTITION_ROUTING_INITSIZE, which is at
odds with the '1' mentioned in the comment. Which is wrong?
(I have a few edits on the patch, so please don't send a full v18 -- a
delta patch would be welcome, if you have further changes to propose.)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: