From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | "K S, Sandhya (Nokia - IN/Bangalore)" <sandhya(dot)k_s(at)nokia(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #15159: Duplicate records for same primary key |
Date: | 2018-04-19 05:27:32 |
Message-ID: | 20180419052732.GB16000@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Apr 18, 2018 at 09:49:35AM -0700, Peter Geoghegan wrote:
> On Wed, Apr 18, 2018 at 3:10 AM, K S, Sandhya (Nokia - IN/Bangalore)
> <sandhya(dot)k_s(at)nokia(dot)com> wrote:
>> Also will postgres has any logs which could be used to identify if this bug has appeared ?
>
> This kind of thing that amcheck's "heapallindexed" option can detect,
> which will appear in Postgres 11. You can get a version with
> equivalent functionality that targets earlier Postgres releases from
> Github (there are official PGDG packages for most Linux systems). The
> heapallindexed check can verify that the heap is consistent with
> indexes.
If you cannot afford to either install or compile this module, then you
can go back to the old dump/restore method, tracking what are the rows
violating constraints when restoring the data taken in the dump.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2018-04-19 09:34:56 | BUG #15162: individual user can connect from anywhere with pgadmin |
Previous Message | Andrew Gierth | 2018-04-19 02:50:52 | Re: Ignored join clause |