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

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: wise(at)wiredgeek(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15959: 'DROP EXTENSION pglogical' while an unused logical replication slot exists causes slot corruption
Date: 2019-08-19 07:12:25
Message-ID: 02366a7a-ffee-d0b3-80e3-d291b44693ce@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2019-08-19 07:15:54 Re: BUG #15961: psql should be able to read password from stdin
Previous Message Bansal, Abhishek (Abhishek) 2019-08-19 06:16:01 Postgresql Query