| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Gregory S(dot) Williamson" <gsw(at)globexplorer(dot)com> |
| Cc: | "Talha Khan" <talha(dot)amjad(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Runtime error: could not open segment 1 of relation ... |
| Date: | 2006-09-26 22:36:38 |
| Message-ID: | 1083.1159310198@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Gregory S. Williamson" <gsw(at)globexplorer(dot)com> writes:
>> 2006-09-26 10:02:15.124 PDT 1387333718 ERROR: could not open segment 1 of
>> relation 1663/43801/7274801 (target block 478216192): No such file or
>> directory
This is most likely caused by trying to follow a bogus item pointer in
an index. If the problem went away after a restart, the bogus value
could not have been on disk but must have been in a bad in-memory copy
of an index page. Which suggests a hardware glitch ... although if you
are using contrib/ltree, I recall seeing several bug fixes go by
recently that were described as fixing potential ltree-index corruption
issues.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory S. Williamson | 2006-09-26 23:22:07 | Re: Runtime error: could not open segment 1 of relation ... |
| Previous Message | Talha Khan | 2006-09-26 22:33:06 | Re: Runtime error: could not open segment 1 of relation ... |