Skip to content

Commit 1948760

Browse files
author
Alicja Kucharczyk
committed
fixing links
1 parent d8bbe46 commit 1948760

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/postgresql/flexible-server/concepts-read-replicas-promote.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,11 @@ It's important to note that if the former primary server enters an irrecoverable
8181

8282
When dealing with multiple replicas and if the primary region lacks a [paired region](concepts-read-replicas-geo.md# paired-regions-for-disaster-recovery-purposes), a special consideration must be considered. In the event of a regional outage affecting the primary, any other replicas won't be automatically recognized by the newly promoted replica. While applications can still be directed to the promoted replica for continued operation, the unrecognized replicas remain disconnected during the outage. These extra replicas will only reassociate and resume their roles once the original primary region has been restored.
8383

84+
## Frequently asked questions
8485

86+
* **If I have an HA-enabled primary and a read replica, and I promote the replica, then switch back to the original primary, will the server still be in HA?**
87+
88+
No, we disable HA during the initial promotion since we do not support HA-enabled read replicas. Promoting a read replica to a primary means that the original primary is changing its role to a replica. If you are switching back, you will need to enable HA on your original primary server.
8589

8690
## Related content
8791

0 commit comments

Comments
 (0)