On Tue, Jul 30, 2013 at 9:28 PM, Andres Freund <andres@2ndquadrant.com>wrote:
> Any chance you could https://github.com/snaga/xlogdump that and the
> neighbouring segments? That might tell us whether we're dealing with
> broken locking or possibly disk corruption (doesn't sound too likely).
>
Actually, we did find what looks like some pretty crazy disk corruption
after I reported this (heap tuple data in pg_clog files). I'm surprised
Postgres did not wig out more, actually. I can run xlogdump later this week
if it's still of interest, but I'm pretty satisfied that this was not
Postgres' fault.
Incidentally, the system performed admirably in the course of the recovery,
considering the severely compromised state of heap and clog data. I'm
really glad we're using Postgres.