Re: BUG #15959: 'DROP EXTENSION pglogical' while an unused logical replication slot exists causes slot corruption

Sorry for the delay - in my test case, I don't specify the version of
pglogical (
https://github.com/diranged/postgres-logical-replication-pgclass-bug/blob/master/Dockerfile#L4)
In the case that we hit in production, this was actually on an Amazon RDS
database, so I am unsure of the specific pglogical version that we were
running. We were using Postgres 10.6 though.

On Mon, Aug 19, 2019 at 12:12 AM Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:

> On 2019-08-14 23:35, PG Bug reporting form wrote:
> > Short Description:
> > If you have a logical replication slot created (but not being actively
> > consumed from) and you issue a 'DROP EXTENSION pglogical', it puts the
> > database into a bad state. Later when the consumer for that slot comes in
> > and tries to start replicating they will receive the following error:
> >
> > pg_recvlogical: unexpected termination of replication stream: ERROR:
> > could not find pg_class entry for 16387
> >
> > Detailed Setup:
> > To replicate the issue fully, check out the code at
> > https://github.com/diranged/postgres-logical-replication-pgclass-bug and
> > follow the instructions.
>
> What version of pglogical are you using?
>
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>