Ganesan R <[EMAIL PROTECTED]> writes:
> We've able recreate the problem on another platform;
It seems pretty dang odd that you should be able to reproduce the
problem on two different platforms, when no one else has reported it
at all. Can you think of anything unusual that might be shared by
the
Ganesan R <[EMAIL PROTECTED]> writes:
> I am using 7.3.2. postmaster prints this on starting up:
> LOG: ReadRecord: bad resource manager data checksum in record at 0/E42144
> pg_resetxlog is able to recover from the problem; but I am concerned because
> I can reproduce the scenario very easily.
Folks,
This bug in 7.2.3 and 7.3.0 seems to have been fixed as a side effect of some
of the other fixes in 7.2.4 and 7.3.2. We're not sure exactly *how*, but the
bug occurs on 7.2.3 and not on 7.2.4.
Did anybody do anything to patch dependancy tracking 7.2.3 ==> 7.2.4?
--
-Josh Berkus
_
Hi,
I am using 7.3.2. postmaster prints this on starting up:
LOG: database system was interrupted at 2003-02-20 14:23:36 IST
LOG: ReadRecord: bad resource manager data checksum in record at 0/E42144
LOG: invalid primary checkpoint record
LOG: ReadRecord: bad resource manager data checksu
