From: Massimo Ortensi <mortensi@unimaticaspa.it>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Dropping database in replica
Date: Sun, 11 Oct 2020 13:26:17 +0200
Message-ID: <1kRZUa-000EMT-Lp@unimaticaspa.it> (raw)
In-Reply-To: <5a3a8be1138b856f5af6b934f2f34bdd9a901a4d.camel@cybertec.at>
References: <1kQrX8-000DtR-G0@unimaticaspa.it>
<5a3a8be1138b856f5af6b934f2f34bdd9a901a4d.camel@cybertec.at>
No, replication is running correctly, and the databases existing in the
master are up to date
Unfortunately replication db logs of the drop database date have been
rewritten
Il 09/10/2020 17.04, Laurenz Albe ha scritto:
>
> There must be something that broke replication.
> Look into the PostgreSQL log of the standby server.
>
> Yours,
> Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mortensi@unimaticaspa.it, pgsql-admin@lists.postgresql.org
Subject: Re: Dropping database in replica
In-Reply-To: <1kRZUa-000EMT-Lp@unimaticaspa.it>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox