| From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
|---|---|
| To: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: New function to show index being vacuumed |
| Date: | 2023-06-22 15:55:27 |
| Message-ID: | CAEze2Wh-7C+-OPMOhPkaRuW4Qptxd4ceFc0R+OkVNG96tFMd8w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 22 Jun 2023 at 16:45, Imseih (AWS), Sami <simseih(at)amazon(dot)com> wrote:
>
> Hi,
>
> [1] is a ready-for-committer enhancement to pg_stat_progress_vacuum which exposes
> the total number of indexes to vacuum and how many indexes have been vacuumed in
> the current vacuum cycle.
>
> To even further improve visibility into index vacuuming, it would be beneficial to have a
> function called pg_stat_get_vacuum_index(pid) that takes in a pid and returns the
> indexrelid of the index being processed.
I'm sorry for not having read (and not reading) the other thread yet,
but what was the reason we couldn't store that oid in a column in the
pg_s_p_vacuum-view?
Could you summarize the other solutions that were considered for this issue?
Kind regards,
Matthias van de Meent
Neon, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Imseih (AWS), Sami | 2023-06-22 16:22:17 | Re: New function to show index being vacuumed |
| Previous Message | Nathan Bossart | 2023-06-22 15:43:01 | Re: allow granting CLUSTER, REFRESH MATERIALIZED VIEW, and REINDEX |