From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Graeme B. Bell <grb@skogoglandskap.no>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: postgres hot-standby questions.
Date: Thu, 26 Mar 2015 10:18:06 -0600
Message-ID: <06AC2E5A-2205-4CF5-82E6-9C35FBDDBF7F@elevated-dev.com> (raw)
In-Reply-To: <8A0640B6-CE88-4E03-B145-0B6149DE7173@skogoglandskap.no>
References: <848F3721-4A21-4260-9640-8F698E3EE376@skogoglandskap.no>
<3C08D5DD-0702-4136-BBE3-21CBE064ADDE@elevated-dev.com>
<A8D5B7E4-31EF-4C5B-B0CC-F6514B50C79B@skogoglandskap.no>
<8A0640B6-CE88-4E03-B145-0B6149DE7173@skogoglandskap.no>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On Mar 26, 2015, at 10:08 AM, Graeme B. Bell <grb@skogoglandskap.no> wrote:
>
> Assuming that you have your server configured with 1 or more hot standbys.
> Are there situations where it is smart & sane to allow a controlled (slow, not emergency) shutdown to complete asynchronously without knowing if any standby got the last bits of wal?
Sure.
Point updates. Shut down 9.4.0. Immediately re-start 9.4.1 on the same cluster.
OS security update, reboot server, PG shuts down and re-starts on boot.
Etc.
I don't care in those cases what the state of the network and my remote replicas are. The replication is interrupted briefly, and then resumes.
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, grb@skogoglandskap.no
Subject: Re: postgres hot-standby questions.
In-Reply-To: <06AC2E5A-2205-4CF5-82E6-9C35FBDDBF7F@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox