Re: Logical replication stuck in catchup state - Mailing list pgsql-general

From Michael Lewis
Subject Re: Logical replication stuck in catchup state
Date
Msg-id CAHOFxGoKhdJyVrnQ-awE1HYjuQK3S4v556ch9fWdhO6yyDxrow@mail.gmail.com
Whole thread Raw
In response to Logical replication stuck in catchup state  (Dan shmidt <dshmidt@hotmail.com>)
List pgsql-general
I don't know if it would be relevant to this problem, but you are missing almost 1 full year of bug fixes. 11.4 was released on 20 June last year. Upgrading minor versions asap is recommended.

I do see this in the release notes from 11.8 last month (https://www.postgresql.org/docs/release/11.8/)-

Ensure that a replication slot's io_in_progress_lock is released in failure code paths (Pavan Deolasee)
--This could result in a walsender later becoming stuck waiting for the lock.

pgsql-general by date:

Previous
From: Dan shmidt
Date:
Subject: Logical replication stuck in catchup state
Next
From: Peter Eisentraut
Date:
Subject: Re: Logical replication stuck in catchup state