| From: | Scott Marlowe <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jakub Ouhrabka <jouh8664(at)ss1000(dot)ms(dot)mff(dot)cuni(dot)cz>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: FATAL: stuck spinlock |
| Date: | 2002-05-02 20:47:42 |
| Message-ID: | Pine.LNX.4.33.0205021447100.5658-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
It's also possible you have some file corruption left over from running
with bad RAM. I would backup the database, reinstall postgresql, then
restore the database as well. No reason to chance it.
On Thu, 2 May 2002, Tom Lane wrote:
> Jakub Ouhrabka <jouh8664(at)ss1000(dot)ms(dot)mff(dot)cuni(dot)cz> writes:
> > Is there anything I can do for further investigation?
>
> I'd suggest trying to verify or disprove your suspicions of bad RAM.
> Run memory tests, warm the chips with a hairdryer and test again,
> that sort of thing.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2002-05-02 20:59:54 | Re: What popular, large commercial websites run |
| Previous Message | Tina Messmann | 2002-05-02 19:14:06 | pg_dump -t and mixed case table names |