| From: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Procedure after failover |
| Date: | 2014-09-26 16:00:13 |
| Message-ID: | CA+6hpamD56sJu9samzvAiGKXKYzHuE4UnHMC4xVAXMeUa7FGbw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
A bit more info:
> What if there were changes on the master that didn't get replicated
> before I originally shut it down?
It looks like Ubuntu's init.d script does a "fast" shutdown, i.e.
SIGINT on this page:
http://www.postgresql.org/docs/9.3/static/server-shutdown.html
I can't tell from the doc what happens re WAL archives though. Is that
what the page means by "online backup mode"? My suspicion is that
because I shut down the master "fast", I'm going to have to wipe it
and then pg_restore it from the slave, because it might have data that
never made it out to the slave. Is that correct?
Thanks,
Paul
--
_________________________________
Pulchritudo splendor veritatis.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raymond O'Donnell | 2014-09-26 16:11:19 | Re: PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device |
| Previous Message | Paul Jungwirth | 2014-09-26 15:47:10 | Procedure after failover |