| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Darren Reed <darrenr+postgres(at)fastmail(dot)net> |
| Cc: | Shoaib Mir <shoaibmir(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: How to reindex when unable to open relation? |
| Date: | 2008-02-26 07:09:21 |
| Message-ID: | 26317.1204009761@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Darren Reed <darrenr+postgres(at)fastmail(dot)net> writes:
> Tom Lane wrote:
>> ...
>> There's no info here to suggest exactly what went wrong; Darren, do you
>> want to fess up to any hardware problems, tripped-over power cords, or
>> such? What PG version is this anyway?
> This is 8.2.6... and I'm starting to believe the hardware is just borked,
> with all of the other troubles I've had.
Well, there are no known data-loss bugs in 8.2.6, with of course the
operative word being "known" ...
> In an earlier bringup of the database, I received an error intended for
> Linux kernels on a BSD box about a page not being zero...
Yeah, I know exactly which message you mean; it was a defense against a
bug that was present for a relatively short time in a few Linux kernel
versions, and could only be exposed on multi-CPU hardware even so.
If you're seeing that and other problems on a BSD kernel then I agree
that hardware issues seem like a likely explanation. Have you tried
running memtest86 and any other hardware diagnostics you can lay your
hands on?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-02-26 07:30:19 | Re: Latest postgres stable version |
| Previous Message | Darren Reed | 2008-02-26 06:59:56 | Re: How to reindex when unable to open relation? |