Re: [HACKERS] Reducing pg_ctl's reaction time - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: [HACKERS] Reducing pg_ctl's reaction time
Date
Msg-id CAMkU=1wseiPuLnT=gYuY9OGurVy9KjUKRoUHUKPFXNnW2+X9wQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Reducing pg_ctl's reaction time  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Jun 29, 2017 at 11:39 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Jeff Janes <jeff.janes@gmail.com> writes:
> In the now-committed version of this, the 'pg_ctl start' returns
> successfully as soon as the server reaches a consistent state. Which is OK,
> except that it does the same thing when hot_standby=off.  When
> hot_standby=off, I would expect it to wait for the end of recovery before
> exiting with a success code.

Um, won't it be waiting forever with that definition?

                        regards, tom lane

No, this isn't streaming.  It hits the PITR limit (recovery_target_*), or runs out of archived wal, and then it opens for business.


Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Reducing pg_ctl's reaction time
Next
From: Amit Khandekar
Date:
Subject: Re: [HACKERS] UPDATE of partition key