| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
| Cc: | Asif Naeem <anaeem(dot)it(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add shutdown_at_recovery_target option to recovery.conf |
| Date: | 2014-11-19 13:13:43 |
| Message-ID: | CA+U5nMJNn3xUcVFpV+Phm6JcuiJpCPgNDvsdrVHDWp_WU7yU9A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18 November 2014 22:05, Petr Jelinek <petr(at)2ndquadrant(dot)com> wrote:
> OK, promote works for me as well, I attached patch that changes continue to
> promote so you don't have to find and replace everything yourself. The
> changed doc wording probably needs to be checked.
I've reworded docs a little.
Which led me to think about shutdown more.
If we ask for PAUSE and we're not in HotStandby it just ignores it,
which means it changes into PROMOTE. My feeling is that we should
change that into a SHUTDOWN, not a PROMOTE. I can raise that
separately if anyone objects.
Also, for the Shutdown itself, why are we not using
kill(PostmasterPid, SIGINT)?
That gives a clean, fast shutdown rather than what looks like a crash.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-11-19 13:22:07 | Re: tracking commit timestamps |
| Previous Message | Magnus Hagander | 2014-11-19 12:36:22 | Re: SSL information view |