| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Syed, Rahila" <Rahila(dot)Syed(at)nttdata(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com>, "PostgreSQL-development (pgsql-hackers(at)postgresql(dot)org)" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] VACUUM Progress Checker. |
| Date: | 2015-10-22 13:54:51 |
| Message-ID: | CA+TgmoYv60+sqTT2aCu418Vczehh3Zy0jVcOSOcP7Q4Hp08f2A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 20, 2015 at 4:58 AM, Syed, Rahila <Rahila(dot)Syed(at)nttdata(dot)com> wrote:
>>I think that you should add the flag or something which indicates whether this backend is running VACUUM or not, into PgBackendStatus.
>>pg_stat_vacuum_progress should display the entries of only backends with that flag set true. This design means that you need to set the flag to true when starting VACUUM and reset at the end of VACUUM progressing.
> Please find attached updated patch which adds a flag in PgBackendStatus which indicates whether this backend in running VACUUM.
Flag isn't reset on error.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-10-22 14:33:42 | Re: Checkpoint throttling issues |
| Previous Message | Robert Haas | 2015-10-22 13:52:25 | Re: Checkpoint throttling issues |