Re: Duplicate values found when reindexing unique index

"Mason Hale" <masonhale(at)gmail(dot)com> writes:
>> I think you misread Mason's post of 20:23 GMT-6 where he says the
>> created_at values are the *same*, not different. Mason's previous bug
>> report 3724 also had duplicate rows with matching created_at values.

> Yes, to confirm, the created_at values are the same. The *only* values that
> are different are updated_at and that value is set via trigger.

Which still demonstrates that they aren't exact images. I'd still like
to see the pg_filedump output though ...

> Last week I had turned my attention away from the database restore, and
> didn't notice that our standby server had exited recovery mode on 12/20.
> Here's the last few lines from the log file (full log attached).

> 2007-12-20 04:11:43 CST () LOG: restored log file
> "000000010000042200000057" from archive
> 2007-12-20 04:13:09 CST () LOG: restored log file
> "000000010000042200000058" from archive
> 2007-12-20 04:14:40 CST () LOG: restored log file
> "000000010000042200000059" from archive
> 2007-12-20 04:14:40 CST () LOG: invalid info bits 0001 in log file 1058,
> segment 89, offset 0

Do you by any chance still have 000000010000042200000058 and
000000010000042200000059 archived? If so it would be useful to
look at the first dozen lines of "od -x" dump of each of them.

regards, tom lane