> -----Original Message----- > From: Christopher Kings-Lynne [mailto:[EMAIL PROTECTED] > Sent: Friday, January 23, 2004 12:29 PM > To: PostgreSQL-development > Cc: Tom Lane > Subject: [HACKERS] Disaster! > > > We ran out of disk space on our main server, and now I've freed up > space, we cannot start postgres! > > Jan 23 12:18:50 canaveral postgres[563]: [2-1] LOG: > checkpoint record > is at 2/96500B94 > Jan 23 12:18:50 canaveral postgres[563]: [3-1] LOG: redo > record is at > 2/964BD23C; undo record is at 0/0; shutdown FALSE > Jan 23 12:18:50 canaveral postgres[563]: [4-1] LOG: next transaction > ID: 14216463; next OID: 4732327 > Jan 23 12:18:50 canaveral postgres[563]: [5-1] LOG: database > system was > not properly shut down; automatic recovery in progress > Jan 23 12:18:50 canaveral postgres[563]: [6-1] LOG: redo starts at > 2/964BD23C > Jan 23 12:18:51 canaveral postgres[563]: [7-1] PANIC: could > not access > status of transaction 14286850 > Jan 23 12:18:51 canaveral postgres[563]: [7-2] DETAIL: could > not read > from file "/usr/local/pgsql/data/pg_clog/000D" at offset 163840: > Undefined error: 0 > Jan 23 12:18:51 canaveral postgres[567]: [1-1] FATAL: the database > system is starting up > Jan 23 12:18:52 canaveral postgres[558]: [1-1] LOG: startup process > (PID 563) was terminated by signal 6 > Jan 23 12:18:52 canaveral postgres[558]: [2-1] LOG: aborting startup > due to startup process failure > > What can I do?
I would restore from backup. Just start an empty database on another machine. ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
