Re: Add index scan progress to pg_stat_progress_vacuum

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Justin Pryzby <pryzby(at)telsasoft(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: 2023-02-24 06:16:10
Message-ID: CAD21AoAmJjfxe8HMd-zVtcaWzvYN=e8s=YPWg9nPBQb-ite2mw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 21, 2023 at 1:48 AM Imseih (AWS), Sami <simseih(at)amazon(dot)com> wrote:
>
> Thanks!
>
> > I think PROGRESS_VACUUM_INDEXES_TOTAL and
> > PROGRESS_VACUUM_INDEXES_PROCESSED are better for consistency. The rest
> > looks good to me.
>
> Took care of that in v25.

Thanks! It looks good to me so I've marked it as Ready for Committer.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2023-02-24 07:11:38 Re: Proposal: :SQL_EXEC_TIME (like :ROW_COUNT) Variable (psql)
Previous Message Dean Rasheed 2023-02-24 06:08:38 Doc updates for MERGE