Hi Shoaib,
Tried with pg_resetxlog
[postgres@dbarhel564 bin]$ pg_resetxlog /usr/local/pgsql/mypg/
The database server was not shut down cleanly.
Resetting the transaction log might cause data to be lost.
If you want to proceed anyway, use -f to force reset.
[postgres@dbarhel564 bin]$ pg_resetxlog -f /usr/local/pgsql/mypg/
Transaction log reset
[postgres@dbarhel564 bin]$ pg_ctl start
server starting
[postgres@dbarhel564 bin]$ LOG: database system was shut down at 2010-04-12 12:26:15 IST
FATAL: could not access status of transaction 889
DETAIL: Could not read from file "pg_clog/0000" at offset 0: Success.
LOG: startup process (PID 1335) exited with exit code 1
LOG: aborting startup due to startup process failure
[postgres@dbarhel564 bin]$
Regards
Raghavendra
On Wed, Apr 14, 2010 at 12:14 PM, Shoaib Mir
<shoaibmir@gmail.com> wrote:
Hi,
Log file
=====
LOG: database system was interrupted; last known up at 2010-04-12 10:53:12 IST
LOG: database system was not properly shut down; automatic recovery in progress
LOG: record with zero length at 0/1A0003C8
LOG: redo is not required
FATAL: could not access status of transaction 889
DETAIL: Could not read from file "pg_clog/0000" at offset 0: Success.
LOG: startup process (PID 303) exited with exit code 1
LOG: aborting startup due to startup process failure
Try using pg_resetxlog to reset the control info on the DB cluster. Once you have done that try re-starting and hopefully that should work then, but you will I think lose everything from the last checkpoint by using pg_resetxlog.
Shoaib Mir
http://shoaibmir.wordpress.com/