| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reducing pg_ctl's reaction time |
| Date: | 2017-06-29 18:49:43 |
| Message-ID: | CAMkU=1wseiPuLnT=gYuY9OGurVy9KjUKRoUHUKPFXNnW2+X9wQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 29, 2017 at 11:39 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jeff Janes <jeff(dot)janes(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Khandekar | 2017-06-29 19:52:11 | Re: UPDATE of partition key |
| Previous Message | Tom Lane | 2017-06-29 18:39:09 | Re: Reducing pg_ctl's reaction time |