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 3d2a935f-850f-47ce-82bf-c2025552e8ab@e-blokos.com
Whole thread Raw
In response to Re: Reuse an existing slot with a new initdb  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On 5/14/2020 6:33 AM, Tom Lane wrote:
> Support <admin@e-blokos.com> 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.
>
>             regards, tom lane
>
>
Ah ok, so there is no way to make physical <--> logical copy jumping 
so... :(



pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Practical usage of large objects.
Next
From: Eduard Rozenberg
Date:
Subject: vacuumdb --jobs deadlock: how to avoid pg_catalog ?