Re: [HACKERS] ANALYZE command progress checker

Поиск
Список
Период
Сортировка
От vinayak
Тема Re: [HACKERS] ANALYZE command progress checker
Дата
Msg-id 8c81db3c-50bd-1722-96fc-3187c71aa1b2@lab.ntt.co.jp
обсуждение исходный текст
Ответ на Re: [HACKERS] ANALYZE command progress checker  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Список pgsql-hackers
On 2017/03/06 17:02, Amit Langote wrote:
> Hi Vinayak,
>
> On 2017/02/28 18:24, vinayak wrote:
>> The attached patch reports the different phases of analyze command.
>> Added this patch to CF 2017-03.
> In the updated monitoring.sgml:
>
> +    <row>
> +     <entry><literal>computing heap stats</literal></entry>
> +     <entry>
> +       <command>VACUUM</> is currently computing heap stats.
> +     </entry>
> +    </row>
> +    <row>
> +     <entry><literal>computing index stats</literal></entry>
> +     <entry>
> +       <command>VACUUM</> is currently computing index stats.
> +     </entry>
> +    </row>
> +    <row>
> +     <entry><literal>cleaning up indexes</literal></entry>
> +     <entry>
> +       <command>ANALYZE</> is currently cleaning up indexes.
> +     </entry>
> +    </row>
> +   </tbody>
> +   </tgroup>
> +  </table>
>
> The entries mentioning VACUUM should actually say ANALYZE.
Yes. Thank you.
I will fix it.

Regards,
Vinayak Pokale
NTT Open Source Software Center



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

Предыдущее
От: Ashutosh Bapat
Дата:
Сообщение: Re: [HACKERS] dropping partitioned tables without CASCADE
Следующее
От: Kyotaro HORIGUCHI
Дата:
Сообщение: Re: [HACKERS] Restricting maximum keep segments by repslots