| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | "K S, Sandhya (Nokia - IN/Bangalore)" <sandhya(dot)k_s(at)nokia(dot)com> |
| Cc: | "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>, "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-18 16:49:35 |
| Message-ID: | CAH2-WzkN1kwjj17vQVD=yzM4G1cOdS_0zNfUJYgDm_aJWHRm6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Karlsson | 2018-04-18 23:34:47 | Ignored join clause |
| Previous Message | K S, Sandhya (Nokia - IN/Bangalore) | 2018-04-18 10:10:00 | Re: BUG #15159: Duplicate records for same primary key |