| From: | Rajan <rajan(at)intercept-india(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | heap_update_redo: no block error in pgsql 7.1 |
| Date: | 2002-02-15 18:09:25 |
| Message-ID: | 5.0.0.25.0.20020215233719.00afa160@intercept-india.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
hi,
i faced this error after vaccum. please help.
DEBUG: database system was interrupted being in recovery at 2002-02-15
12:55:51
EST
This propably means that some data blocks are corrupted
and you will have to use last backup for recovery.
DEBUG: CheckPoint record at (5, 1864040592)
DEBUG: Redo record at (5, 1864040592); Undo record at (0, 0); Shutdown TRUE
DEBUG: NextTransactionId: 13855178; NextOid: 26051231
DEBUG: database system was not properly shut down; automatic recovery in
progre
ss...
DEBUG: redo starts at (5, 1864040656)
FATAL 2: heap_update_redo: no block
postmaster: Startup proc 13311 exited with status 512 - abort
postmaster: invalid argument -- wal_debug
Try 'postmaster --help' for more information.
regards
rajan
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/plain | 168 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-02-15 21:50:44 | Re: Maintaining the list of release changes |
| Previous Message | Tom Lane | 2002-02-15 17:45:39 | Re: "Bug" in statistics for v7.2? |