Re: Logical replication stuck in catchup state

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Dan shmidt <dshmidt(at)hotmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Logical replication stuck in catchup state
Date: 2020-06-09 21:45:28
Message-ID: CAHOFxGoKhdJyVrnQ-awE1HYjuQK3S4v556ch9fWdhO6yyDxrow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2020-06-09 22:21:00 Re: Logical replication stuck in catchup state
Previous Message Dan shmidt 2020-06-09 21:30:38 Logical replication stuck in catchup state