| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Rahila Syed <rahilasyed90(at)gmail(dot)com>, "Syed, Rahila" <Rahila(dot)Syed(at)nttdata(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] VACUUM Progress Checker. |
| Date: | 2015-07-16 01:21:49 |
| Message-ID: | 55A7072D.8040505@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-07-16 AM 05:18, Rahila Syed wrote:
>
> GUC parameter 'pgstat_track_progress' is currently PGC_SUSET in line with
> 'track_activities' GUC parameter.
Naming the GUC pgstat* seems a little inconsistent. It could be called,
say, track_maintenance_progress_interval/track_vacuum_progress_interval.
That way, it will look similar to existing track_* parameters:
#track_activities = on
#track_counts = on
#track_io_timing = off
#track_functions = none # none, pl, all
#track_activity_query_size = 1024 # (change requires restart)
Also, adding the new GUC to src/backend/utils/misc/postgresql.conf.sample
might be helpful.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-07-16 02:35:10 | Re: [PATCH] postgres_fdw extension support |
| Previous Message | Tomas Vondra | 2015-07-16 00:27:01 | Re: Memory Accounting v11 |