Re: Reuse an existing slot with a new initdb

On 5/14/2020 6:33 AM, Tom Lane wrote: Support writes: I think David caught it, the question is Why, as long as we have an exact copy of the master (from pg_dumpall) Stop right there. pg_dumpall does *not* produce an exact copy. It produces a logically equivalent copy, which is not close eno

Re: Reuse an existing slot with a new initdb

Support writes: > I think David caught it, the question is Why, as long as we have an > exact copy of the master (from pg_dumpall) Stop right there. pg_dumpall does *not* produce an exact copy. It produces a logically equivalent copy, which is not close enough for physical replication to work.

Re: Reuse an existing slot with a new initdb

On 5/13/2020 9:28 PM, David G. Johnston wrote: On Wednesday, May 13, 2020, Michael Paquier > wrote: On Wed, May 13, 2020 at 02:12:45PM -0700, live-school support wrote: > I didn't recal that it was not possible to create a hot standby with a fresh > n

Reuse an existing slot with a new initdb

On Wednesday, May 13, 2020, Michael Paquier wrote: > On Wed, May 13, 2020 at 02:12:45PM -0700, live-school support wrote: > > I didn't recal that it was not possible to create a hot standby with a > fresh > > new install and pg_dumpall :(. > > > > only pg_basebackup or an exact copy of the data f

Re: Reuse an existing slot with a new initdb

On Wed, May 13, 2020 at 02:12:45PM -0700, live-school support wrote: > I didn't recal that it was not possible to create a hot standby with a fresh > new install and pg_dumpall :(. > > only pg_basebackup or an exact copy of the data folder can do it right? is > the reason technical or else? When u

Re: Reuse an existing slot with a new initdb

On 5/13/2020 1:24 PM, Laurenz Albe wrote: On Wed, 2020-05-13 at 06:18 -0700, Support wrote: 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

Re: Reuse an existing slot with a new initdb

On 5/13/2020 1:24 PM, Laurenz Albe wrote: On Wed, 2020-05-13 at 06:18 -0700, Support wrote: 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

Re: Reuse an existing slot with a new initdb

Best Regards LIVE-SCHOOL FOUNDATION http://www.live-school.net in...@live-school.net On 5/13/2020 1:24 PM, Laurenz Albe wrote: On Wed, 2020-05-13 at 06:18 -0700, Support wrote: 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 re

Re: Reuse an existing slot with a new initdb

On Wed, 2020-05-13 at 06:18 -0700, Support wrote: > 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 > > so

Re: Reuse an existing slot with a new initdb

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 optio

Reuse an existing slot with a new initdb

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 an