From: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | New function to show index being vacuumed |
Date: | 2023-06-22 14:44:43 |
Message-ID: | 4B54F427-454D-4910-AE61-E04F899091E6@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
Currently the only way to get the index being vacuumed by a process
Is through os tools such as pstack.
I had a patch for this as part of [1], but it was decided to handle this in a separate
discussion.
Comments/feedback will be appreciated before sending out a v1 of the patch.
Regards,
Sami Imseih
Amazon Web Services (AWS)
1. https://www.postgresql.org/message-id/flat/5478DFCD-2333-401A-B2F0-0D186AB09228(at)amazon(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2023-06-22 15:43:01 | Re: allow granting CLUSTER, REFRESH MATERIALIZED VIEW, and REINDEX |
Previous Message | Tomas Vondra | 2023-06-22 14:16:06 | Re: memory leak in trigger handling (since PG12) |