Re: Add index scan progress to pg_stat_progress_vacuum

From: Greg Stark <stark(at)mit(dot)edu>
To: "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>
Cc: "Bossart, Nathan" <bossartn(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add index scan progress to pg_stat_progress_vacuum
Date: 2021-12-16 22:03:23
Message-ID: CAM-w4HM8PD=3ATj4CnVZcmJTNRsintcA61LQ94WmJF7h7UaLzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I had a similar question. And I'm still not clear from the response
what exactly index_blks_total is and whether it addresses it.

I think I agree that a user is likely to want to see the progress in a
way they can understand which means for a single index at a time.

I think what you're describing is that index_blks_total and
index_blks_scanned are the totals across all the indexes? That isn't
clear from the definitions but if that's what you intend then I think
that would work.

(For what it's worth what I was imagining was having a pair of
counters for blocks scanned and max blocks in this index and a second
counter for number of indexes processed and max number of indexes. But
I don't think that's necessarily any better than what you have)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2021-12-16 22:40:43 Re: row filtering for logical replication
Previous Message Imseih (AWS), Sami 2021-12-16 21:37:11 Re: Add index scan progress to pg_stat_progress_vacuum