On 29/10/10 10:27, Tom Lane wrote:
Were there similar warnings on the master? Uninitialized-page warnings
are expected in certain error-recovery scenarios, but I'd be a little
worried if the slave appeared to be out of sync with the master.
I don't see any in the logs - however the relevant table may not have
been vacuum recently enough to spit out the warning. I do see lots of these:
2010-09-30 17:31:20 NZDT ERROR: could not open relation with OID 1836671
2010-09-30 17:31:20 NZDT ERROR: could not open relation with OID 1836671
and also the following has recently started appearing on the console:
kernel: [ 7341.689322] ECC/ChipKill ECC error.
So... lots of brokeness to examine here (have promoted one of our slaves
to be the new master). I'll see if we still have the old master db
around, it would be interesting to see what happens if we start it up
and try a VACUUM - however the dbas may have set the box up as a slave
again before we noticed the memory errors (so possibly deleted the old
master).
Cheers
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
