2

I've got a PostgreSQL Replication set up using Repmgr.

Replication works fine, until one of the databases is deleted on the master node.

Standby replica throws off 'WAL cannot be found' error and disconnects from the Upstream which causes a major issue for the failover system. Standby replicas won't recover unless postgres directory is wiped clean and the database is fully cloned from the master again.

PostgreSQL version: 12.5

Repmgr version: 5.1.0

System: CentOS 7

Any help would be appreciated!

Improve this question
3
  • 1
    Please quote the exact error messages from the log verbatim.
    – Laurenz Albe
    Jun 2, 2021 at 9:19
  • Dropping databases works fine with replication. It does not even generate much WAL. Whatever your problem is (which you haven't given enough details about) is probably merely coincidental to the database drop.
    – jjanes
    Jun 2, 2021 at 14:52
  • "2021-06-03 14:18:40.235 CEST [66313] LOG: started streaming WAL from primary at E46/EC000000 on timeline 1 2021-06-03 14:18:40.235 CEST [66313] FATAL: could not receive data from WAL stream: ERROR: requested WAL segment 0000000100000E46000000EC has already been removed " This is the kind of error that I get in postgres log
    – David Petric
    Jun 3, 2021 at 12:19

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.