From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Amit Langote <amitlangote09(at)gmail(dot)com>, pokurev(at)pm(dot)nttdata(dot)co(dot)jp, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, bannos(at)nttdata(dot)co(dot)jp |
Subject: | Re: [PROPOSAL] VACUUM Progress Checker. |
Date: | 2016-03-08 15:24:41 |
Message-ID: | CA+TgmoZPFf=ZLqt7vrskXMT7zj9dpD3acAQs_AqQWYK5oT-=Dw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 8, 2016 at 3:02 AM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Updated versions attached.
>
> * changed st_progress_param to int64 and so did the argument of
> pgstat_progress_update_param(). Likewise changed param1..param10 of
> pg_stat_get_progress_info()'s output columns to bigint.
>
> * Added back the Oid field st_command_target and corresponding function
> pgstat_progress_set_command_target(Oid).
What the heck do we have an SQL-visible pg_stat_reset_local_progress()
for? Surely if we ever need that, it's a bug.
I think pgstat_progress_update_param() should Assert(index >= 0 &&
index < N_PROGRESS_PARAM). But I'd rename N_PROGRESS_PARAM to
PGSTAT_NUM_PROGRESS_PARAM.
Regarding "XXX - privilege check is maybe dubious" - I think the
privilege check here should match pg_stat_activity. If it does,
there's nothing dubious about that IMHO.
This patch has been worked on by so many people and reviewed by so
many people that I can't keep track of who should be credited when it
gets committed. Could someone provide a list of author(s) and
reviewer(s)?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2016-03-08 15:25:08 | Re: The plan for FDW-based sharding |
Previous Message | Alvaro Herrera | 2016-03-08 15:14:08 | Re: Recovery test failure for recovery_min_apply_delay on hamster |