Re: BUG #13935: Duplicate row in pg_constraint table which is not accessible via indexes

From: Andres Freund <andres(at)anarazel(dot)de>
To: bear2k(at)mail(dot)ru
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13935: Duplicate row in pg_constraint table which is not accessible via indexes
Date: 2016-02-10 21:25:36
Message-ID: 20160210212536.2qtvzaqkc7p5tp3h@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2016-02-08 16:32:22 +0000, bear2k(at)mail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Сергей Гавриленко 2016-02-11 00:07:26 Re: BUG #13941: Different value "pg_constraint.consrc" for similar Check Constrait
Previous Message Tom Lane 2016-02-10 18:01:38 Re: BUG #13935: Duplicate row in pg_constraint table which is not accessible via indexes