Re: Reuse an existing slot with a new initdb
От | Support |
---|---|
Тема | Re: Reuse an existing slot with a new initdb |
Дата | |
Msg-id | 48699aec-7736-6b8a-cd92-fe6d93db6a78@e-blokos.com обсуждение исходный текст |
Ответ на | Reuse an existing slot with a new initdb (Support <admin@e-blokos.com>) |
Ответы |
Re: Reuse an existing slot with a new initdb
|
Список | 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 по дате отправления: