Feedback-ID: i374947ac:Fastmail
Content-Type: multipart/alternative;
 boundary="------------jkUtijYyVU0uAFDs0cWXZGn9"
Message-ID: <348796e3-9777-4294-9b20-fec4e5a89135@quadratum-braccas.com>
Date: Tue, 24 Mar 2026 17:27:06 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: pgsql-admin@lists.postgresql.org
Content-Language: en-US
From: Sbob <sbob@quadratum-braccas.com>
Subject: logical replication failing after a crash of the publisher
Archived-At: 
 <https://www.postgresql.org/message-id/348796e3-9777-4294-9b20-fec4e5a89135%40quadratum-braccas.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------jkUtijYyVU0uAFDs0cWXZGn9
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

All;


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 recovered the VM we were able to start the db and it came 
online after an online recovery, however we are now getting these 
entries (see below) in the log on the publisher and no row changes are 
showing up on the subscriber


2026-03-24 23:14:09.845 UTC [102580] postgres@claimsprocess STATEMENT: 
  START_REPLICATION SLOT "prod_sub" LOGICAL 9AE6/4E2F5740 (proto_version 
'4', origin 'any', publication_names '"prod_pub"')
2026-03-24 23:14:09.959 UTC [102580] postgres@claimsprocess LOG:  could 
not send data to client: Connection reset by peer
2026-03-24 23:14:09.959 UTC [102580] postgres@claimsprocess CONTEXT: 
  slot "prod_sub", output plugin "pgoutput", in the change callback, 
associated LSN 9AE6/4B83E5A8


we tried disabling and then enabling the subscription followed by a 
REFRESH PUBLICATION but the issue is un changed


Thanks in advance for any help

--------------jkUtijYyVU0uAFDs0cWXZGn9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>All;</p>
    <p><br>
    </p>
    <p>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 recovered the VM we were able to start the db
      and it came online after an online recovery, however we are now
      getting these entries (see below) in the log on the publisher and
      no row changes are showing up on the subscriber</p>
    <p><br>
    </p>
    <p>
      <span style="font-family:monospace"><span
          style="color:#000000;background-color:#ffffff;">2026-03-24
          23:14:09.845 UTC [102580] postgres@claimsprocess STATEMENT:
           START_REPLICATION SLOT "prod_sub" LOGICAL 9AE6/4E2F5740
          (proto_version '4', origin 'any', publication_names
          '"prod_pub"')</span><span
          style="color:#000000;background-color:#ffffff;">
        </span><br>
        <span style="color:#000000;background-color:#ffffff;">2026-03-24
          23:14:09.959 UTC [102580] postgres@claimsprocess LOG:  could
          not send data to client: Connection reset by peer</span><span
          style="color:#000000;background-color:#ffffff;">
        </span><br>
        <span style="color:#000000;background-color:#ffffff;">2026-03-24
          23:14:09.959 UTC [102580] postgres@claimsprocess CONTEXT:
           slot "prod_sub", output plugin "pgoutput", in the change
          callback, associated LSN 9AE6/4B83E5A8</span><br>
        <span style="color:#000000;background-color:#ffffff;">
        </span><br>
      </span>
      <br>
    </p>
    <p>we tried disabling and then enabling the subscription followed by
      a REFRESH PUBLICATION but the issue is un changed</p>
    <p><br>
    </p>
    <p>Thanks in advance for any help</p>
  </body>
</html>

--------------jkUtijYyVU0uAFDs0cWXZGn9--