Re: Autovacuum on partitioned table

Поиск
Список
Период
Сортировка
От yuzuko
Тема Re: Autovacuum on partitioned table
Дата
Msg-id CAKkQ509Gn8bOEZNmcudBYj=g97qG4PcNC2pbGxC4Ci_pPtQrEQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Autovacuum on partitioned table  (Amit Langote <amitlangote09@gmail.com>)
Ответы Re: Autovacuum on partitioned table  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Re: Autovacuum on partitioned table  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: Autovacuum on partitioned table  (Amit Langote <amitlangote09@gmail.com>)
Список pgsql-hackers
Hi,

Thanks for reviewing the patch.

> > We can make it work correctly but I think perhaps we can skip updating
> > statistics values of partitioned tables other than n_mod_since_analyze
> > as the first step. Because if we support also n_live_tup and
> > n_dead_tup, user might get confused that other statistics values such
> > as seq_scan, seq_tup_read however are not supported.
>
> +1, that makes sense.
>
Yes, Indeed.  I modified it not to update statistics other than
n_mod_since_analyze.
Attach the v5 patch.  In this patch, pgstat_report_analyze() always reports 0 as
msg.m_live_tuples and m_dead_tuples when the relation is partitioned.

-- 
Best regards,
Yuzuko Hosoya
NTT Open Source Software Center

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [PATCH] pg_upgrade: report the reason for failing to open thecluster version file
Следующее
От: John Naylor
Дата:
Сообщение: truncating timestamps on arbitrary intervals