We had a secondary server. The secondary we were using was basically dead. That's what lead to the problem. We were trying to fix it, but ran the wrong procedu

We had a secondary server. The secondary we were using was basically dead. That's what lead to the problem. We were trying to fix it, but ran the wrong procedure on the primary instead of the secondary Thus wiping the primary, instead of what might have been left on the secondary. The secondary was already removed at that point. Basically the procedure was the following: 1. Secondary falls behind too much, stops replicating. At this point you need to manually re-sync the whole thing 2. A re-sync requires an empty PostgreSQL data directory, so this data was removed 3. Re-sync doesn't work, leading to the other problems 4. At some point team-member-1 thought previous re-sync attempts left data behind, so team-member-1 wiped the data directory again to be sure; except team-member-1 ran this on db1.cluster.gitlab.com (the primary) instead of db2.cluster.gitlab.com (the secondary)