Re: BUG #14940: Duplicated records inspite of primary key and unique constraint

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Сергей А(dot) Фролов <sergey(dot)frolov(at)smetarik(dot)ru>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14940: Duplicated records inspite of primary key and unique constraint
Date: 2017-12-04 18:19:08
Message-ID: d3dbeb59-67ac-9044-54d0-6df9259fb899@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 12/04/2017 05:06 PM, Сергей А. Фролов wrote:
> I have scanned all pages for tran numbers 370881,370882,364507 .
>
> It looks like 364507 is the number of restore transaction.
>
> Is it possible that  370881,370882 are the numbers of failed maintenance
> jobs like vacuum or rindex?
>

I don't think any of those operations create new rows in the heap.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message dap 2017-12-04 20:10:55 BUG #14945: postmaster deadlock while logging after syslogger exited
Previous Message Сергей А. Фролов 2017-12-04 16:06:07 Re: BUG #14940: Duplicated records inspite of primary key and unique constraint