| From: | Jan Peters <haseningo(at)gmx(dot)de> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | PostgreSQL replication failover |
| Date: | 2021-01-13 08:27:59 |
| Message-ID: | trinity-64a56362-8af1-4ec9-b408-d4256ce65fd2-1610526479876@3c-app-gmx-bs17 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hello,
we are running postgresqlserver on s390 zLinux machines. The distribution is RedHat 7 and RedHat 8, so we do not have the many x86 tools available.
We always run 2 instances with a replication (streaming) async mode, the replica is in hot_standby and we use it for read-only accesses. About the setup we have the following question:
How is an orderly failover accomplished? Our current procedure is.
1. primary stop
2. promote replica to primary
3. create standby.signal on old primary
4. change primary_conninfo on old primary
5. start old primary as new replica
Is this processing correct? Are there any other steps that simplify a failover? How can we be sure that all changes have been transferred from the old master to the replica?
thanks in advance
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2021-01-13 11:25:35 | Re: PostgreSQL replication failover |
| Previous Message | Bruce Momjian | 2021-01-09 18:06:27 | Re: I need to complex Query - need big support |