Postgres Pro
Downloads
Home   >   mailing lists

Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby - Mailing list pgsql-admin

From Ron
Subject Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby
Date
Msg-id dd83b495-616f-1e03-585d-e76930c6cdd5@gmail.com
Whole thread Raw
In response to Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby  (Ian Lawrence Barwick <barwick@gmail.com>)
Responses Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby  (Noah <noah-list@enabled.com>)
List pgsql-admin
Tree view 
On 2/12/22 6:35 PM, Ian Lawrence Barwick wrote:
[snip]

> You appear to be starting a database which is not a copy of the primary node it
binary copy
> is trying to connect to. It's impossible to tell from the provided information
> how that happened. Possibly you have more than one instance on the standby
> (replica) and are somehow starting the wrong one. If not you'll need to make
> a backup of the primary and make sure that's what is being started.

Binary copy using pg_basebackup (or something like pgbackrest).

-- 
Angular momentum makes the world go 'round.

pgsql-admin by date:

Previous
From: Ian Lawrence Barwick
Date:
Subject: Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby
Next
From: Noah
Date:
Subject: Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby