PANIC: unable to locate a valid checkpoint record - Mailing list pgsql-bugs

From Ganesan R
Subject PANIC: unable to locate a valid checkpoint record
Date
Msg-id 20030220092720.GA31822@andiamo.com
Whole thread Raw
Responses Re: [ADMIN] PANIC: unable to locate a valid checkpoint record  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
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 checksum in record at 0/E42104
LOG:  invalid secondary checkpoint record
PANIC:  unable to locate a valid checkpoint record
LOG:  startup process (pid 7530) was terminated by signal 6
LOG:  aborting startup due to startup process failure
----

pg_resetxlog is able to recover from the problem; but I am concerned because
I can reproduce the scenario very easily. I originally encountered the
problem in 7.2.1; tried upgrading to 7.2.4 and now 7.3.2 and this scenario
happens for every version.

The scenario is like this;

I have an application that is doing database updates using JDBC. I do a
kill -9 on postmaster. The application detects that postmaster is down
and restarts it; I do kill -9 on postmaster. After a couple of such
forced crashes postmaster refuses to come up. The application uses a
PostgreSQL 7.2 JDBC2 driver.

I wrote a python application and tried to recreate the problem but wasn't
successful. However, I can consistently reproduce the problem with the
Java application. Any suggestions on how I can proceed?

Please CC me on any replies; I am not (yet) subscribed to the lists. Thanks.

Ganesan

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: setting time zone during a transaction causes time warp
Next
From: Josh Berkus
Date:
Subject: Re: Function will not back up on 7.2.3