Re: logical replication - negative bitmapset member not allowed - Mailing list pgsql-general

From Tom Lane
Subject Re: logical replication - negative bitmapset member not allowed
Date
Msg-id 17747.1554213563@sss.pgh.pa.us
Whole thread Raw
In response to Re: logical replication - negative bitmapset member not allowed  (Tim Clarke <tim.clarke@minerva.info>)
Responses Re: logical replication - negative bitmapset member not allowed  (Tim Clarke <tim.clarke@minerva.info>)
List pgsql-general
Tim Clarke <tim.clarke@minerva.info> writes:
> Dang. I just replicated ~380 tables. One was missing an index so I
> paused replication, added a unique key on publisher and subscriber,
> re-enabled replication and refreshed the subscription.

Well, that's not much help :-(.  Can you provide any info to narrow
down where this is happening?  I mean, you haven't even told us whether
it's the primary or the slave that is complaining.  Does it seem to
be associated with any particular command?  (Turning on log_statement
and/or log_replication_commands would likely help with that.)  Does
data seem to be getting transferred despite the complaint?  If not,
what's missing on the slave?

            regards, tom lane



pgsql-general by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: CVE-2019-9193 about COPY FROM/TO PROGRAM
Next
From: Tim Clarke
Date:
Subject: Re: logical replication - negative bitmapset member not allowed