| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bojan Belovic <bbelovic(at)usa(dot)net> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: db recovery (FATAL 2) |
| Date: | 2002-05-08 16:46:00 |
| Message-ID: | 3233.1020876360@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Bojan Belovic <bbelovic(at)usa(dot)net> writes:
> You are correct, it's 7.1.2 . However, the problem is not with disk space
> (there's several gigs available), but there could be a problem with a bad
> sector on one of the log files. If this is the case, and the log file is
> corrupted, is there any way of recovering, even with a certain data loss?
Hm. It's complaining about a write, not a read, so there is no lost
data (yet), even if your theory is correct. You might first try copying
the entire $PGDATA/pg_xlog directory somewhere else.
If nothing else avails, see contrib/pg_resetxlog. But that should be
your last resort not first.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bojan Belovic | 2002-05-08 20:27:17 | Re: db recovery (FATAL 2) |
| Previous Message | Jean-Luc Lachance | 2002-05-08 16:15:56 | Performance on update from join |