Re: Reboot standby - Mailing list pgsql-novice
As long as the streaming replication is in asynchronous mode, you can restart the standby anytime without affecting the primary. You can check whether replication is synchronous or asynchronous with "select sync_state from pg_stat_replication;"
If it says 'synchronous', you will have to first change it to asynchronous before you can reboot the standby, or else all commits on primary will be pending waiting for the replica to replicate those commits first
On Mon, Feb 26, 2018 at 1:07 PM, Thomas W. Ekberg <tekberg@uw.edu> wrote:
We have 2 postgres servers, a primary and standby. One of our DB admins noticed a "health indicator" alert light on our standby which means "system degraded." She logged into the iLO and it lists the Cache Module Status as Failed. This needs to be repaired (we have an idea on what needs to be done) and most likely will require a reboot of our standby server.
We use streaming replication and from what I can see, that is initiated by the standby server. What are the shutdown and restart considerations for our standby server?
Attachment
pgsql-novice by date: