Skip to content
This repository has been archived by the owner on Nov 18, 2017. It is now read-only.

database system identifier differs between the primary and standby? #14

Closed
tvb opened this issue May 18, 2015 · 2 comments
Closed

database system identifier differs between the primary and standby? #14

tvb opened this issue May 18, 2015 · 2 comments

Comments

@tvb
Copy link

tvb commented May 18, 2015

What does this mean?

FATAL:  database system identifier differs between the primary and standby
DETAIL:  The primary's identifier is 6150202608832133854, the standby's identifier is 6150207001805245765.
@Winslett
Copy link
Contributor

This should never happen unless you are running different clusters trying to talk to each other. For example, you initialize clusters A and B separately. Then, you try to attach a follower from cluster B to cluster A.

This could happen in Governor if you have two clusters sharing a namespace.

@tvb
Copy link
Author

tvb commented May 20, 2015

Hmmm well I have not seen it again since I reinstalled the cluster. So lets not spent anymore time on this.

@tvb tvb closed this as completed May 20, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants