| From: | Antonin Houska <ah(at)cybertec(dot)at> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | bharath(dot)rupireddyforpostgres(at)gmail(dot)com, mihailnikalayeu(at)gmail(dot)com, adam8157(at)gmail(dot)com |
| Subject: | Allow progress tracking of sub-commands |
| Date: | 2026-06-29 11:57:26 |
| Message-ID: | 106920.1782734246@localhost |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I've noticed several complaints about two commands trying to report their
progress at the same time, overwriting each other's output [1][2][3]. I posted
a prototype of an enhancement of the monitoring infrastructure that allows for
progress reporting of two commands w/o conflicts [4].
This is a new version that passes regression tests. I'll register it for the
upcoming CF.
[1] https://www.postgresql.org/message-id/5667.1774513434%40localhost
[2] https://www.postgresql.org/message-id/CALj2ACUgwSchK6jQ2CdKLBWUADTOE_zKdTff2Zg3E6hOuXKv-w%40mail.gmail.com
[3] https://www.postgresql.org/message-id/aj4gJQMba0kClQmj%40Mac
[4] https://www.postgresql.org/message-id/30939.1777888333%40localhost
--
Antonin Houska
Web: https://www.cybertec-postgresql.com
| Attachment | Content-Type | Size |
|---|---|---|
| v01-0001-Allow-progress-tracking-of-sub-commands.patch | text/x-diff | 36.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2026-06-29 12:04:24 | clean up size_t/ssize_t use with POSIX file system APIs |
| Previous Message | Nisha Moond | 2026-06-29 11:54:36 | Re: Proposal: Conflict log history table for Logical Replication |