Help with data recovery... (pg_controldata output)

output of pg_controldata was:


bash-2.03$ ../bin/pg_controldata
pg_control version number:            71
Catalog version number:               200201121
Database state:                       IN_RECOVERY
pg_control last modified:             Thu May 16 21:59:45 2002
Current log file id:                  4
Next log file segment:                164
Latest checkpoint location:           3/FACBFA78
Prior checkpoint location:            3/FABD4720
Latest checkpoint's REDO location:    3/FACBFA78
Latest checkpoint's UNDO location:    0/0
Latest checkpoint's StartUpID:        7
Latest checkpoint's NextXID:          6174305
Latest checkpoint's NextOID:          30144904
Time of latest checkpoint:            Tue May 14 09:22:12 2002
Database block size:                  8192
Blocks per segment of large relation: 131072
LC_COLLATE:                           C
LC_CTYPE:                             C
bash-2.03$

postmaster messages:
DEBUG:  database system was interrupted being in recovery at 2002-05-16 21:34:20 IST
        This probably means that some data blocks are corrupted
        and you will have to use the last backup for recovery.
DEBUG:  checkpoint record is at 3/FACBFA78
DEBUG:  redo record is at 3/FACBFA78; undo record is at 0/0; shutdown FALSE
DEBUG:  next transaction id: 6174305; next oid: 30144904
DEBUG:  database system was not properly shut down; automatic recovery in progress
DEBUG:  redo starts at 3/FACBFAB8






On Thursday 16 May 2002 09:40 pm, Rajesh Kumar Mallah. wrote:
> Hi ,
>
> my postmaster is refusing to startup. and my last backup is 18 hrs old.
> restoring data for that backup is the last option i have.
>
> I have already tried pg_resetxlog -f $PGDATA , but that sets the
> database to a state that is 2 days old.
>
> will anyone please help me with my best bet in recovering data
> for $PGDATA
>
>  i made a copy of it before running pg_resetxlog.
>
> DEBUG:  database system was interrupted being in recovery at 2002-05-16
> 21:34:20 IST This probably means that some data blocks are corrupted
>         and you will have to use the last backup for recovery.
> DEBUG:  checkpoint record is at 3/FACBFA78
> DEBUG:  redo record is at 3/FACBFA78; undo record is at 0/0; shutdown FALSE
> DEBUG:  next transaction id: 6174305; next oid: 30144904
> DEBUG:  database system was not properly shut down; automatic recovery in
> progress DEBUG:  redo starts at 3/FACBFAB8

--
Rajesh Kumar Mallah,
Project Manager (Development)
Infocom Network Limited, New Delhi
phone: +91(11)6152172 (221) (L) ,9811255597 (M)

Visit http://www.trade-india.com ,
India's Leading B2B eMarketplace.