Thread: want to drop corrupt db
After a db restore failed for reasons having to do with lack of disk space, when I try to restart the DB, I get...
dfg_suse> postmaster -D /proj/cad_sserv/cellibcmp/daveg/Postgres/DB -i > /proj/cad_sserv/cellibcmp/daveg/Postgres/postmaster.log &
[1] 29644
dfg_suse> 2007-08-02 14:17:14 LOG: database system was interrupted while in recovery at 2007-08-02 14:16:21 EDT
HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2007-08-02 14:17:14 LOG: checkpoint record is at B/258A7100
2007-08-02 14:17:14 LOG: redo record is at A/A700B9C0; undo record is at 0/0; shutdown FALSE
2007-08-02 14:17:14 LOG: next transaction ID: 64132; next OID: 73638687
2007-08-02 14:17:14 LOG: database system was not properly shut down; automatic recovery in progress
2007-08-02 14:17:14 PANIC: could not fsync control file: Disk quota exceeded
2007-08-02 14:17:14 LOG: startup process (PID 29647) was terminated by signal 6
2007-08-02 14:17:14 LOG: aborting startup due to startup process failure
[1] Exit 1 postmaster -D /proj/cad_sserv/cellibcmp/daveg/Postgres/DB -i > ...
dfg_suse>
If the DB is trashed, how can I just delete it and start from scratch?
Thanks
-dave
"Gauthier, Dave" <dave.gauthier@intel.com> writes:
> After a db restore failed for reasons having to do with lack of disk
> space, when I try to restart the DB, I get...
> 2007-08-02 14:17:14 PANIC: could not fsync control file: Disk quota
> exceeded
> If the DB is trashed, how can I just delete it and start from scratch?
Why do you conclude that the DB is trashed? Looks to me like you just
need to fix the disk space problem.
regards, tom lane