| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tim Clarke <tim(dot)clarke(at)minerva(dot)info>, PostgreSQL General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: logical replication - negative bitmapset member not allowed |
| Date: | 2019-04-04 21:37:04 |
| Message-ID: | 4a16af4e-ba61-e46d-6d69-0a20ef7ed97d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2019-04-01 23:43, Alvaro Herrera wrote:
> Maybe the replica identity of a table got set to a unique index on oid?
> Or something else involving system columns? (If replication is
> otherwise working, the I suppose there's a separate publication that's
> having the error; the first thing to isolate would be to see what tables
> are involved in that publication).
Looking through the code, the bms_add_member() call in
logicalrep_read_attrs() does not use the usual
FirstLowInvalidHeapAttributeNumber offset, so that seems like a possible
problem.
However, I can't quite reproduce this. There are various other checks
that prevent this scenario, but it's plausible that with a bit of
whacking around you could hit this error message.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-04-04 21:43:24 | Re: Seeded Replication |
| Previous Message | Justin Pryzby | 2019-04-04 21:26:13 | Re: query logging of prepared statements |