Re: logical replication - negative bitmapset member not allowed
Tim Clarke <tim.clarke@minerva.info>
From: Tim Clarke <tim.clarke@minerva.info>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, PostgreSQL General
List <pgsql-general@postgresql.org>
Date: 2019-04-04T22:05:50Z
Lists: pgsql-general
On 04/04/2019 22:37, Peter Intrauterine wrote: > 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. > Promise I've not been whacking around...... Tim Clarke Main: +44 (0)1376 503500 | Fax: +44 (0)1376 503550 Web: https://www.manifest.co.uk/ Minerva Analytics Ltd 9 Freebournes Court | Newland Street | Witham | Essex | CM8 2BL | England ---------------------------------------------------------------------------------------------------------------------------- Copyright: This e-mail may contain confidential or legally privileged information. If you are not the named addressee you must not use or disclose such information, instead please report it to admin@minerva.info<mailto:admin@minerva.info> Legal: Minerva Analytics is the trading name of: Minerva Analytics Ltd: Registered in England Number 11260966 & The Manifest Voting Agency Ltd: Registered in England Number 2920820 Registered Office at above address. Please Click Here >><https://www.manifest.co.uk/legal/> for further information.
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