| From: | Christopher Cashell <topher-pgsql(at)zyp(dot)org> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)qwest(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problems restarting after database crashed (signal |
| Date: | 2004-07-01 07:45:08 |
| Message-ID: | 20040701074508.GB5380@zyp.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
At Wed, 30 Jun 04, Unidentified Flying Banana Scott Marlowe, said:
> The combination of a Sig 11 failure and a process stuck in a D state
> makes me lean towards thinking it's bad hardware (CPU or memory). Have
> you tested this machine?
It's possible that it's bad hardware, as the machine is a little long in
the tooth. However, at the same time, it is a *very* well tested box.
It's been in production use for 4 years, and I have yet to experience a
significant hardware issue.
Up until this, prior to when I rebooted it a few hours ago over this
issue, it had been running for 110 days, with the database running
(under approximately the same load) for that whole time.
If it *is* a hardware problem, I would have expected it to show up
somewhat sooner than this.
--
| Christopher
+------------------------------------------------+
| Here I stand. I can do no other. |
+------------------------------------------------+
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Najib Abi Fadel | 2004-07-01 07:47:38 | Bug in function to_char() !! |
| Previous Message | Shridhar Daithankar | 2004-07-01 07:31:23 | Re: Dump / restore for optimization? |