Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 2A5B19FC3A9 for ; Fri, 18 May 2007 14:01:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 74875-04 for ; Fri, 18 May 2007 14:01:42 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by postgresql.org (Postfix) with ESMTP id 34FDC9FC3F4 for ; Fri, 18 May 2007 14:01:43 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id k3so455679ugf for ; Fri, 18 May 2007 10:01:42 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=K11uAoLEBDTqgCmt06ttmiPy2Q0AevJKNAtK47kpjO+CxlJEI0K+v1nUjAlzuxmNEuprMAOuJXQzMV2tJMqsZDQkhbvVNFYzimA+F+aagCkSixKXy6gchRbe7Tw2jt2IzxwY8gYKhqEVAeV8/06Npxvc32QhJ+c8t5SIoCgATyg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=CFxxHVUHz/i8TNiF6EFdhy6dp3LSuCraWoku4GN0zeWLMwg9mURHUStdluBkEkogrTT6PATNpclT1WKMXhwF3Gl15KxIwSgMfl17CInojTawpaguGO6OVaT2sCwUVBKApt8rUhcdSIIhWIopPzg5Ai0iJt/aKodoeUd4WSj0OiA= Received: by 10.67.116.15 with SMTP id t15mr1162617ugm.1179507702030; Fri, 18 May 2007 10:01:42 -0700 (PDT) Received: from ?192.168.1.95? ( [89.251.0.64]) by mx.google.com with ESMTP id k28sm2634954ugd.2007.05.18.10.01.40; Fri, 18 May 2007 10:01:40 -0700 (PDT) Message-ID: <464DDBE1.7060900@gmail.com> Date: Fri, 18 May 2007 19:01:21 +0200 From: Stephane Bailliez User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 CC: pgsql-admin@postgresql.org Subject: Re: Frequent pg_clog on system References: <464D7B05.4040109@gmail.com> <1179499248.41472.212.camel@soundwave.pgh.priv.collaborativefusion.com> <464DCA08.50303@gmail.com> <29499.1179507412@sss.pgh.pa.us> In-Reply-To: <29499.1179507412@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/198 X-Sequence-Number: 25518 Tom Lane wrote: > Stephane Bailliez 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