| From: | Support <admin(at)e-blokos(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Reuse an existing slot with a new initdb |
| Date: | 2020-05-13 13:18:38 |
| Message-ID: | 48699aec-7736-6b8a-cd92-fe6d93db6a78@e-blokos.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Basques, Bob (CI-StPaul) | 2020-05-13 13:33:30 | RE: Enforcing uniqueness on [real estate/postal] addresses |
| Previous Message | Laurenz Albe | 2020-05-13 11:35:06 | Re: what is the best way to access cold data on another server? |