Message-ID: <369bd0be354c979bca79aeffb948ae81ee236dbd.camel@cybertec.at>
Subject: Re: logical replication failing after a crash of the publisher
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Sbob <sbob@quadratum-braccas.com>, pgsql-admin@lists.postgresql.org
Date: Wed, 25 Mar 2026 06:46:31 +0100
In-Reply-To: <348796e3-9777-4294-9b20-fec4e5a89135@quadratum-braccas.com>
References: <348796e3-9777-4294-9b20-fec4e5a89135@quadratum-braccas.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/369bd0be354c979bca79aeffb948ae81ee236dbd.camel%40cybertec.at>
Precedence: bulk

On Tue, 2026-03-24 at 17:27 -0600, Sbob wrote:
> we have logical replication setup for a set of tables that took 4 days to=
 finish
> the initial sync, the publisher server crashed, after the cloud team reco=
vered
> the VM we were able to start the db and it came online after an online re=
covery,
> however we are now getting these entries (see below) in the log on the pu=
blisher
> and no row changes are showing up on the subscriber
>
> =C2=A0STATEMENT: =C2=A0START_REPLICATION SLOT "prod_sub" LOGICAL 9AE6/4E2=
F5740 (proto_version '4', origin 'any', publication_names '"prod_pub"')=20
> =C2=A0LOG: =C2=A0could not send data to client: Connection reset by peer=
=20
> =C2=A0CONTEXT: =C2=A0slot "prod_sub", output plugin "pgoutput", in the ch=
ange callback, associated LSN 9AE6/4B83E5A8
>=20
> we tried disabling and then enabling the subscription followed by a REFRE=
SH PUBLICATION
> but the issue is un changed

That seems to be the log from the publisher.  It shows that the subscriber =
closed the
connection unexpectedly.  You should examine the subscriber's log for the r=
eason.

Yours,
Laurenz Albe