From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Maciek Sakrejda <maciek(at)heroku(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #8656: Duplicate data violating unique constraints |
Date: | 2013-12-05 09:15:29 |
Message-ID: | 20131205091529.GD28793@alap2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2013-12-04 21:29:21 -0800, Maciek Sakrejda wrote:
> Interesting. That very well could be the issue. I didn't this affected
> primaries.
Well, it's a different, 9.3 only,bug, to the replication one.
> Latest checkpoint's NextXID: 0/1579944
> Latest checkpoint's NextMultiXactId: 592631
>
> From the description, I can't tell what this means: does this either confim
> or refute that this database was affected?
It doesn't say anything definitive either way. Do you run with any
non-default settings? Possibly vacuum_freeze_min_age,
vacuum_freeze_table_age, autovacuum_freeze_max_age?
Could you do:
SELECT ctid FROM post WHERE rows_re_affected;
That will spin out a bunch of rows like '(page,item)'.
With that page could you do:
CREATE EXTENSION pageinspect;
SELECT * FROM page_header(get_raw_page('post', page_from_above));
SELECT * FROM heap_page_items(get_raw_page('post', page_from_above));
and post that here?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-12-05 09:59:49 | Re: BUG #8647: Backend process hangs and becomes unkillable when SSL client looses connection |
Previous Message | d.shumilov | 2013-12-05 09:07:33 | BUG #8658: Errors during restore database |