Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby
Date: 2022-02-13 01:03:45
Message-ID: dd83b495-616f-1e03-585d-e76930c6cdd5@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Noah 2022-02-13 02:02:29 Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby
Previous Message Ian Lawrence Barwick 2022-02-13 00:35:38 Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby