| From: | Sbob <sbob(at)quadratum-braccas(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | logical replication failing after a crash of the publisher |
| Date: | 2026-03-24 23:27:06 |
| Message-ID: | 348796e3-9777-4294-9b20-fec4e5a89135@quadratum-braccas.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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(at)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(at)claimsprocess LOG: could
not send data to client: Connection reset by peer
2026-03-24 23:14:09.959 UTC [102580] postgres(at)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2026-03-25 05:46:31 | Re: logical replication failing after a crash of the publisher |
| Previous Message | Tom Lane | 2026-03-23 13:57:57 | Re: Technical validation on altering atttypmod for numeric column in PostgreSQL |