| From: | Josef Šimánek <josef(dot)simanek(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | [PATCH v1] Add pg_stat_progress overview view |
| Date: | 2026-11-07 21:54:14 |
| Message-ID: | CAFp7QwqYGVqF7LO6fDTthpaskRYNPaVXSPXKRQOrYT=XMe8kpw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
finding active progress reports currently requires querying each
pg_stat_progress_* view separately.
This patch adds pg_stat_progress with three columns: pid, command, and
progress_view, pointing to the detailed view for each operation. It
reuses the existing infrastructure without backend changes. IMHO,
these are the minimal common fields. I also considered datid and
datname, but some tracked operations, such as base backups, cover the
whole cluster.
Documentation and tests are included. Build, regression, isolation,
and new TAP tests passed locally.
I'd appreciate feedback on the usefulness and proposed columns. My
longer-term aim is to make cluster operations easier to discover and
monitor, and to extend progress reporting to more commands.
Regards,
Josef
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Add-pg_stat_progress-overview-view.patch | text/x-patch | 13.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Bjørge Løvland | 2026-11-07 22:00:19 | Re: Design proposal: grain, exact per-time-bucket aggregates from a summarizing index |
| Previous Message | Ishjaap Singh | 2026-11-07 20:54:55 | psql: Don't offer partitioned tables after CREATE INDEX CONCURRENTLY |