pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Sami Imseih <samimseih@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
Subject: Re: Report index currently being vacuumed in pg_stat_progress_vacuum
Date: Fri, 21 Aug 2026 08:10:35 +0900
Message-ID: <aoeJa9Ap4_MyFX3_@paquier.xyz> (raw)
In-Reply-To: <CALj2ACWWf-zDXpXDZf5fscPq_fwVY=NX+7w4JcObcgXuY9=h+Q@mail.gmail.com>
References: <CALj2ACUgwSchK6jQ2CdKLBWUADTOE_zKdTff2Zg3E6hOuXKv-w@mail.gmail.com>
	<CAA5RZ0vh8cNV0DuTuebCfi=XVkQhYD5TWUx7+DHSE1D56c88-w@mail.gmail.com>
	<CALj2ACU3+seeZKAsH=d_LpVEVRfafnvqDmj3czFf1daOTbXVyw@mail.gmail.com>
	<CAA5RZ0t2vArQ3EpWSqSQekROuKeaonvgOz=Czkp4Q0tS_krscQ@mail.gmail.com>
	<CAA5RZ0sw8ZuAYt+bJ_VvJvcHVKe+=1tstC7oqAqUye9_3Ta6gg@mail.gmail.com>
	<CALj2ACXhLVJh0OeN5W61_UvhyBxH3k98ffXhnRPYr8NsNbMZSw@mail.gmail.com>
	<an6P_WQNCM4P843q@paquier.xyz>
	<CAA5RZ0tbkiEpD0ZBL+ACKO8o5mDkZmZq0PAdABqQt2nNr8MKjQ@mail.gmail.com>
	<CALj2ACWWf-zDXpXDZf5fscPq_fwVY=NX+7w4JcObcgXuY9=h+Q@mail.gmail.com>

On Wed, Aug 19, 2026 at 07:37:00PM -0700, Bharath Rupireddy wrote:
> I don't think a separate view is the right approach at least for two
> reasons. One, to know the progress of a vacuum one has to query two
> views and relate them. Two, since the leader itself participates in
> vacuuming indexes alongside workers (and will also for parallel heap
> vacuum), splitting the same command's progress into two views adds
> complexity. Keeping everything in a single view with one row per
> worker (as discussed upthread) is simpler. Some fields would be null
> on worker rows, but documenting this should be sufficient. That said,
> I'm open to hear more thoughts on this.

Having a single progress view feels like the natural approach here,
for both the leader and the workers.  The leader triggers the
existence of the workers, but both leader and workers may finish by
doing the same job as there could be usually little meaning for a
leader to stand idle, waiting for all the workers to do the work.
Such choices are implementation-agnostic, of course; we should not
lock ourselves.
--
Michael

Attachments:

  [application/pgp-signature] signature.asc (832B, ../aoeJa9Ap4_MyFX3_@paquier.xyz/2-signature.asc)
  download

view thread (39+ messages)  latest in thread

Message-ID: <aoeJa9Ap4_MyFX3_@paquier.xyz>
Permalink:  ../aoeJa9Ap4_MyFX3_@paquier.xyz/
Also on:    postgresql.org/message-id/aoeJa9Ap4_MyFX3_@paquier.xyz

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: michael@paquier.xyz, bharath.rupireddyforpostgres@gmail.com, samimseih@gmail.com, pgsql-hackers@lists.postgresql.org, satyanarlapuram@gmail.com
  Subject: Re: Report index currently being vacuumed in pg_stat_progress_vacuum
  In-Reply-To: <aoeJa9Ap4_MyFX3_@paquier.xyz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox