Re: Autovacuum on partitioned table (autoanalyze)
От | Alvaro Herrera |
---|---|
Тема | Re: Autovacuum on partitioned table (autoanalyze) |
Дата | |
Msg-id | 20210406205649.GA20523@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: Autovacuum on partitioned table (autoanalyze) (Tomas Vondra <tomas.vondra@enterprisedb.com>) |
Ответы |
Re: Autovacuum on partitioned table (autoanalyze)
|
Список | pgsql-hackers |
On 2021-Apr-04, Tomas Vondra wrote: > 1) I still don't understand why inheritance and declarative partitioning > are treated differently. Seems unnecessary nad surprising, but maybe > there's a good reason? I think there is a good reason to treat them the same: pgstat does not have a provision to keep stats both of the table with children, and the table without children. It can only have one of those. For partitioning that doesn't matter: since the table-without-children doesn't have anything on its own (no scans, no tuples, no nothing) then we can just use the entry to store the table-with-children data. But for the inheritance case, the parent can have its own tuples and counts its own scans and so on; so if we change things, we'll overwrite the stats. Maybe in the long-term we should allow pgstat to differentiate those cases, but that seems not in scope for this patch. I'm working on the code to fix the other issues. -- Álvaro Herrera 39°49'30"S 73°17'W
В списке pgsql-hackers по дате отправления: