| From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Status of the startup process post end of recovery |
| Date: | 2013-03-04 12:51:50 |
| Message-ID: | CABOikdOwm4V8JauyNY1Nb=6YjDvAR1T+NdVjaEAkz=+a-z2k5Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Comments ?
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-03-04 12:53:42 | Re: Status of the startup process post end of recovery |
| Previous Message | Boszormenyi Zoltan | 2013-03-04 12:40:38 | Re: Matview patch added rewriteDefine.c.orig to the repository |