Re: logical replication - negative bitmapset member not allowed
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tim Clarke <tim.clarke@minerva.info>
Cc: PostgreSQL General List <pgsql-general@postgresql.org>
Date: 2019-04-02T13:59:23Z
Lists: 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
Commits
-
Fix negative bitmapset member not allowed error in logical replication
- 2e00d5976419 10.11 landed
- 7961da1887af 11.6 landed
- d891d2c89785 12.1 landed
- 1c60e40ad54b 13.0 landed