| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_ctl promote wait |
| Date: | 2016-02-19 19:16:49 |
| Message-ID: | 20160219191649.ql2o6xxws4r3dluj@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-02-20 00:06:09 +0900, Fujii Masao wrote:
> One concern is that there can be a "time" after the pg_control's state
> is changed to DB_IN_PRODUCTION and before the server is able to
> start accepting normal (not read-only) connections. So if users try to
> start write transaction just after pg_ctl promote -w ends, they might
> get an error because the server is still in recovery, i.e., the startup
> process is running.
It might make sense to have one more state type, which is used when
ending recovery, but before full access is allowed.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2016-02-19 19:18:19 | Re: FDW: should GetFdwRoutine be called when drop table? |
| Previous Message | Andres Freund | 2016-02-19 19:15:34 | Re: pg_ctl promote wait |