From: Stephane Bailliez <sbailliez@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Frequent pg_clog on system
Date: Fri, 18 May 2007 19:01:21 +0200
Message-ID: <464DDBE1.7060900@gmail.com> (raw)
In-Reply-To: <29499.1179507412@sss.pgh.pa.us>
References: <464D7B05.4040109@gmail.com>
<1179499248.41472.212.camel@soundwave.pgh.priv.collaborativefusion.com>
<464DCA08.50303@gmail.com>
<29499.1179507412@sss.pgh.pa.us>
Tom Lane wrote:
> Stephane Bailliez <sbailliez@gmail.com> writes:
>
>> FWIW forgot to mention, chance of memory issue is low, memory was
>> entirely changed a couple of days ago while upgrading from 1GB to 4GB
>>
>
> Hmm, did this all start happening after the RAM upgrade? If so I'd say
> the odds are real good that you got some bad memory there.
>
No it was appearing before with only 1GB. So I had hope to leave the
bad memory potential by having this brand new 4GB replacement and it was
ok for a week.
Did not run memtest86+ on it however, so that will be mission next week
I'm afraid.
Overheating is a possibility due to where machine is located right now.
-- stephane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: sbailliez@gmail.com
Subject: Re: Frequent pg_clog on system
In-Reply-To: <464DDBE1.7060900@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox