From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Status of the startup process post end of recovery |
Date: | 2013-03-04 12:53:42 |
Message-ID: | 20130304125342.GC3943@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2013-03-04 18:21:50 +0530, Pavan Deolasee wrote:
> Hello,
>
> While doing some tests, I observed that the "ps" command continues to
> display status of the startup process as "recovering <filename>" even
> though it has finished the redo and is now performing end-of-recovery
> checkpoint. This checkpoint can take a while, a few seconds to a few
> minutes depending on the dirty buffers at the end of the recovery. The
> "ps" command keep displaying a stale status for all that time. How
> about calling set_ps_display() with appropriate status string, say
> similar to what is logged by LogCheckpointStart() ? If we do that,
> what would be the best place to add that code ? I was thinking adding
> that to CreateCheckpoint() itself so that the status is displayed at
> all relevant places.
That might be confusing for example in CREATE DATABASE.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2013-03-04 13:33:53 | Re: Support for REINDEX CONCURRENTLY |
Previous Message | Pavan Deolasee | 2013-03-04 12:51:50 | Status of the startup process post end of recovery |