| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add index scan progress to pg_stat_progress_vacuum |
| Date: | 2022-01-11 22:18:24 |
| Message-ID: | 6067E1B3-07E6-478D-9A6B-B62F5D641EF2@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/11/22, 12:33 PM, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> wrote:
> What about something like "The number of indexes that are eligible for vacuuming".
> This covers the cases where either an individual index is skipped or the entire "index vacuuming" phase is skipped.
Hm. I don't know if "eligible" is the right word. An index can be
eligible for vacuuming but skipped because we set INDEX_CLEANUP to
false. Maybe we should just stick with "The number of indexes that
will be vacuumed." The only thing we may want to clarify is whether
this value will change in some cases (e.g., vacuum failsafe takes
effect).
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-01-11 23:27:21 | Re: [EXTERNAL] Re: PQcancel does not use tcp_user_timeout, connect_timeout and keepalive settings |
| Previous Message | Andrew Dunstan | 2022-01-11 21:35:41 | Re: Windows crash / abort handling |