From: | "Syed, Rahila" <Rahila(dot)Syed(at)nttdata(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | 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-20 08:58:11 |
Message-ID: | C3C878A2070C994B9AE61077D46C38468EE634C0@MAIL703.KDS.KEANE.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
>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.
Also, pgstat_report_progress function is changed to make it generic for all commands reporting progress.
Thank you,
Rahila Syed
______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.
Attachment | Content-Type | Size |
---|---|---|
Vacuum_progress_checker_v5.patch | application/octet-stream | 19.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Feike Steenbergen | 2015-10-20 09:24:47 | Re: SuperUser check in pg_stat_statements |
Previous Message | Amit Kapila | 2015-10-20 08:32:44 | Re: Checkpoint throttling issues |