| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | kallol(at)aworkflow(dot)com, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Bug #920: The PostgreSql Server goes down |
| Date: | 2003-03-26 14:35:13 |
| Message-ID: | 4780.1048689313@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
pgsql-bugs(at)postgresql(dot)org writes:
> FATAL 2: open of /usr/share/postgresql/data/pg_clog/0C81 failed: No such file or directory
This indicates corrupted data --- specifically, a trashed transaction ID
in a row header. In all the cases I've been able to examine, this was
just the first symptom of more widespread corruption (usually, a whole
disk page is trashed). I recommend checking for hardware problems;
you may have bad RAM or a flaky disk drive or cable.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-03-26 15:28:41 | Re: Postgresql 7.3.2 Crash |
| Previous Message | Fabio Furia Silva | 2003-03-26 13:38:25 | Relation n does not exist when trying to ad a foregin key |