Обсуждение: Reboot standby
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?
Вложения
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?
Вложения
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?your master has to keep enough wals that the standby can retrieve them and catch up to the master. there are several solutions to achive that. you can define wal_keep_segments or you can use replication slots. other solutions: using archive_command to store the wals outside from the master. you can also use barman as a wal-hub.
Regards, Andreas