Re: BUG #8656: Duplicate data violating unique constraints
От | Andres Freund |
---|---|
Тема | Re: BUG #8656: Duplicate data violating unique constraints |
Дата | |
Msg-id | 20131205091529.GD28793@alap2.anarazel.de обсуждение исходный текст |
Ответ на | BUG #8656: Duplicate data violating unique constraints (maciek@heroku.com) |
Ответы |
Re: BUG #8656: Duplicate data violating unique constraints
|
Список | 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
В списке pgsql-bugs по дате отправления: