Re: Reuse an existing slot with a new initdb - Mailing list pgsql-general

From Support
Subject Re: Reuse an existing slot with a new initdb
Date
Msg-id 48699aec-7736-6b8a-cd92-fe6d93db6a78@e-blokos.com
Whole thread Raw
In response to Reuse an existing slot with a new initdb  (Support <admin@e-blokos.com>)
Responses Re: Reuse an existing slot with a new initdb  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general
On 5/8/2020 1:51 PM, Support wrote:
> I normalized my replislots with the name of my nodes.
> I have 2 options in my recovery script that tries first pg_basebackup
> to recover and sync the hot standby, but unfortunately big DB fails 
> sometimes due
> to very slow or unstable network. So my second option is to completely 
> make a new inidb and import an sql file from pg_dumpall master as it 
> takes less bytes once compressed. But I'm facing an issue with the 
> slot complaining (obviously) about the ho standby node that does not 
> match the slot identifier. So my question is simple, is there a way to 
> reinitialize the slot to not renew the identifier with the new hot 
> standby initdb?
>
> Thanks
>
> David

No one has an answer to my question?
thanks!

David



pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: what is the best way to access cold data on another server?
Next
From: "Basques, Bob (CI-StPaul)"
Date:
Subject: RE: Enforcing uniqueness on [real estate/postal] addresses