Re: unique index violation after pg_upgrade to PG10

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Kenneth Marshall <ktm(at)rice(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: unique index violation after pg_upgrade to PG10
Date: 2017-10-24 22:27:52
Message-ID: 20171024222752.GW21735@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 24, 2017 at 01:48:55PM -0500, Kenneth Marshall wrote:
> I just dealt with a similar problem with pg_repack and a PostgreSQL 9.5 DB,
> the exact same error. It seemed to caused by a tuple visibility issue that
> allowed the "working" unique index to be built, even though a duplicate row
> existed. Then the next pg_repack would fail with the error you got.

FTR, I was able to run the repack script several times without issue, hitting
that table each time.

Justin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2017-10-24 22:28:40 Re: unique index violation after pg_upgrade to PG10
Previous Message Michael Paquier 2017-10-24 22:17:10 Re: Remove secondary checkpoint