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@ss1000.ms.mff.cuni.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@postgresql.org so that your
> message can get through to the mailing list cleanly
>