From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_ctl promote wait |
Date: | 2016-02-18 08:13:43 |
Message-ID: | CANP8+j+F31J-rKULZ2rPPbNRfC5EpEqp_NseueoE6CMU_+sSXg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 18 February 2016 at 02:47, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> It would be nice if pg_ctl promote supported the -w (wait) option.
>
> How could pg_ctl determine when the promotion has finished?
>
> We could query pg_is_in_recovery(), but that would require database
> access, which we got rid of in pg_ctl.
>
> We could check when recovery.conf is gone or recovery.done appears.
> This could work, but I think some people are trying to get rid of these
> files, so building a feature on that might be a problem? (I think the
> latest news on that was that the files might be different in this
> hypothetical future but there would still be a file to prevent
> re-recovery on restart.)
>
> Other ideas?
>
We use a trigger file under the covers, so a promotion complete file seems
useful also, but crappy.
Perhaps we should have a Server Status file that shows Standby or Master,
obviously not updated on crash.
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Sridhar N Bamandlapally | 2016-02-18 08:26:59 | Re: JDBC behaviour |
Previous Message | Vladimir Sitnikov | 2016-02-18 08:13:39 | Re: [JDBC] JDBC behaviour |