Re: [PATCH v1] Add pg_stat_progress overview view

From: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
To: Josef Šimánek <josef(dot)simanek(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH v1] Add pg_stat_progress overview view
Date: 2026-11-19 16:54:35
Message-ID: CAN12+YLVWH+j8o002xmXFWStaoAA=kKXau7dX_PL838B0mLpGA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Josef,

> finding active progress reports currently requires querying each
> pg_stat_progress_* view separately.

Thanks for the patch. I looked through it, but I'm having trouble
seeing the use case. Since the view only exposes pid, command, and
the name of the detailed view, a monitoring tool would still need to
query that specific view to get anything actionable.

Could you share some real-world scenarios where this would be useful?

--
Sami

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikhil Sontakke 2026-11-19 17:00:11 Re: let ALTER TABLE DROP COLUMN drop whole-row referenced object
Previous Message Ishjaap Singh 2026-11-19 16:37:08 Re: psql: Don't offer partitioned tables after CREATE INDEX CONCURRENTLY