| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Generalize ereport_startup_progress infrastructure |
| Date: | 2022-08-16 21:15:44 |
| Message-ID: | 20220816211544.GB255076@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 10, 2022 at 11:00:20AM -0400, Robert Haas wrote:
> Maybe the checkpointer is a better candidate, but somehow I feel that
> we can't consider this sort of thing separate from the existing
> progress reporting that checkpointer already does. Perhaps we need to
> think of changing or improving that in some way rather than adding
> something wholly new alongside the existing system.
I agree that the checkpointer has a good chance of being a better
candidate. Are you thinking of integrating this into log_checkpoints
somehow? Perhaps this parameter could optionally accept an interval for
logging the progress of ongoing checkpoints.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2022-08-16 21:22:31 | Re: add checkpoint stats of snapshot and mapping files of pg_logical dir |
| Previous Message | Tom Lane | 2022-08-16 21:02:27 | Re: hash_xlog_split_allocate_page: failed to acquire cleanup lock |