| From: | vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ANALYZE command progress checker |
| Date: | 2017-03-06 09:20:04 |
| Message-ID: | 8c81db3c-50bd-1722-96fc-3187c71aa1b2@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2017-03-06 09:20:06 | Re: Restricting maximum keep segments by repslots |
| Previous Message | Ashutosh Bapat | 2017-03-06 09:19:57 | Re: dropping partitioned tables without CASCADE |