Hi Greg!
Thank you for your immediate response. I cannot tell you the xfs_repair
files that were mangled but I did the repair on an lvm snapshot. the files
were not listed in 'select * from pg_class'. Might not be THE source for
inodes needed by the cluster?
I agree, it does not really sonud like
On Mon, Jul 29, 2013 at 10:19 PM, Klaus Ita wrote:
> My feeling is, that 'something' got confused with hot-standby and
> wal_archiving leading to this situation, that seems to be partially xfs
> caused?? xfs_repair mentionned some missing files, that pg did not
> expect to have (maybe truncate