Re: BUG #13935: Duplicate row in pg_constraint table which is not accessible via indexes - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #13935: Duplicate row in pg_constraint table which is not accessible via indexes
Date
Msg-id 20160210212536.2qtvzaqkc7p5tp3h@alap3.anarazel.de
Whole thread Raw
In response to BUG #13935: Duplicate row in pg_constraint table which is not accessible via indexes  (bear2k@mail.ru)
List pgsql-bugs
On 2016-02-08 16:32:22 +0000, bear2k@mail.ru wrote:
> We are seeing a very strange situation - table pg_constrint has a duplicate
> row for particular primary key constraint which is not accessible via
> indexes but is visible during segment scan. There wasn't any specific
> manipulation with catalog data, however the database is used with standby
> node, so switchover from one instance to another is performed from time to
> time.

Did your have any failovers or restore from backup, at some point in the
history of the cluster? If so, what were the exact procedures you used?

Greetings,

Andres Freund

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #13935: Duplicate row in pg_constraint table which is not accessible via indexes
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #13941: Different value "pg_constraint.consrc" for similar Check Constrait