Re: How is this possible "publication does not exist"

From: Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Dave Cramer <davecramer(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: How is this possible "publication does not exist"
Date: 2019-12-20 09:55:25
Message-ID: 20191220105525.1ea05d2e@firost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, 19 Dec 2019 19:19:56 +0100
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:

> On 2019-12-19 19:15, Dave Cramer wrote:
> > It seems that if you drop the publication on an existing slot it needs
> > to be recreated. Is this expected behaviour
> A publication is not associated with a slot. Only a subscription is
> associated with a slot.

Couldn't it be the same scenario I reported back in october? See:

Subject: Logical replication dead but synching
Date: Thu, 10 Oct 2019 11:57:52 +0200

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2019-12-20 10:07:26 Re: Disallow cancellation of waiting for synchronous replication
Previous Message Adam Lee 2019-12-20 09:16:26 Re: Memory-Bounded Hash Aggregation