From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Beena Emerson <memissemerson(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Ryan Murphy <ryanfmurphy(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait |
Date: | 2017-01-18 23:52:29 |
Message-ID: | CAB7nPqTxB9OrJ0RmGK8QFBkM=AoCkRp-uGDR+AxKE37BP+fbtw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 19, 2017 at 6:20 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> On Wed, Jan 18, 2017 at 16:15 Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Wed, Jan 18, 2017 at 3:59 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>> > For non-cold standby configurations, pg_ctl is going to return just as
>> > soon as the database has finished crash recovery, which in most cases
>> > will probably be on the order of a few seconds.
>>
>> /me is poleaxed.
>>
>> Yeah, that was a confused sentence- most of the time it's going to return
>> on the order of a few seconds because we're doing regular startup without
>> having to do any crash recovery.
>>
>>
>> For actual crash recovery cases, it'll take between a few seconds and
>> checkpoint_timeout, as I described up-thread, based on the amount of
>> outstanding WAL.
Recovering up to the minumum recovery point could take minutes!
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-01-18 23:54:56 | Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait |
Previous Message | Michael Paquier | 2017-01-18 23:48:38 | Re: Patch to implement pg_current_logfile() function |