Re: Status of the startup process post end of recovery

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(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 14:30:07
Message-ID: CABOikdMV0u8gOdU9XFrYG7ewYiBFkCB-YUmEQ2sWJ_rPOJQOqQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 4, 2013 at 6:23 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On 2013-03-04 18:21:50 +0530, Pavan Deolasee wrote:
>> 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.
>

Yeah, you're right. StartupXLOG() seems to be a better place in that
case. We can set it before calling CreateCheckpoint() and set it back
to "" once checkpoint finishes. Or we can also set it to report the
next action such as "running recovery_end_command", but not sure if
any step beyond CHECKPOINT would really take long enough to be worth
caring for.

Thanks,
Pavan

--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2013-03-04 14:39:08 Re: LIBPQ Implementation Requiring BYTEA Data
Previous Message Magnus Hagander 2013-03-04 13:38:09 Bug in tm2timestamp