Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1rx80P-006XB0-Rq
	for pgsql-general@arkaria.postgresql.org; Wed, 17 Apr 2024 16:19:29 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1rx80O-00Cl9A-GH
	for pgsql-general@arkaria.postgresql.org; Wed, 17 Apr 2024 16:19:28 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <justin@postgresql.org>)
	id 1rx80O-00Cl91-30
	for pgsql-general@lists.postgresql.org; Wed, 17 Apr 2024 16:19:28 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by magus.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <justin@postgresql.org>)
	id 1rx80H-001U5K-5c
	for pgsql-general@lists.postgresql.org; Wed, 17 Apr 2024 16:19:27 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type:
	Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:MIME-Version:Sender
	:Reply-To:Content-ID:Content-Description;
	bh=kSZUeCG04sH5jlusViHzLLBzaHXBA3jmrK48Nsqr8nM=; b=Xn7cXpm906hNc3VczmGY7Xbpaf
	bX3O8C2AJGWRNoWEBUK1Vt8e3LRK4evTqmbhT6jf5/5nnLvl+uzOJ+mdjfJ2SzEm0Jtnbx1OWt9qF
	QZFMs0E2K1ahvTH03o/wCeeuA38Lx+zZwLPDAdnycdS4Is2BOZ8Y6WAdyTaS6fyXNm/831mFn1K5+
	sXdS9Cajf0zuO8jQwMQsOhwbPN8580niBl/QcpS99wy0QREigdmnJ9HqfFZa04FYR4v08GSdlt3DX
	TFLuzPSH4jHauXClJjUgmPbKmCnguwW/BTYyjYcu4brukkcN1mtXe9lm5RhADA0NOO+QXxxku7D2C
	k6dxxjYA==;
Received: from meldrar.postgresql.org ([87.238.57.231] helo=webmail.postgresql.org)
	by meldrar.postgresql.org with esmtpsa  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <justin@postgresql.org>)
	id 1rx80E-003Juj-2O; Wed, 17 Apr 2024 16:19:20 +0000
MIME-Version: 1.0
Date: Thu, 18 Apr 2024 02:19:17 +1000
From: Justin Clift <justin@postgresql.org>
To: jack <jack4pg@a7q.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: constant crashing hardware issue and thank you TAKE AWAY
In-Reply-To: <dW4aboom8PhJ2SGrC0j20Cl-vbr-TSIO1Qpt25cX9ALawY5rwLOUd3HkUJK5cCEVFS5ZS1AiGVzMpMW7FCFytxKhZZNTHkHyBzlJo3xVw9A=@a7q.com>
References: <dW4aboom8PhJ2SGrC0j20Cl-vbr-TSIO1Qpt25cX9ALawY5rwLOUd3HkUJK5cCEVFS5ZS1AiGVzMpMW7FCFytxKhZZNTHkHyBzlJo3xVw9A=@a7q.com>
User-Agent: Roundcube Webmail/1.4.15
Message-ID: <f18ca15e73ea07a8b196a1e6cc04bcd6@postgresql.org>
X-Sender: justin@postgresql.org
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/f18ca15e73ea07a8b196a1e6cc04bcd6%40postgresql.org>
Precedence: bulk

On 2024-04-17 23:06, jack wrote:
<snip>
> As a result of this I will be checking the RAM on all my machines once
> a month or the moment a machine starts to act strange.

Once a month is overkill, and unlikely to be useful. :)

With server or enterprise grade hardware, it'll support "ECC" memory.

That has extra memory chips + supporting circuity on the memory board
so it can detect + correct most errors which happen without them causing
problems.

For the errors that it can't *correct*, it'll still generate warnings
to your system software to let you know (if you've configured it).

If you do get such a warning - or if the system starts acting funny like
you saw - that's when you'd want to run memtest on the system.

---

The other time to run memtest on the system is when you first buy or
receive a new server.  You'd generally do a "burn in" test of all the
things (memory, hard disks/ssds, cpu, gpu, etc) just to make sure
everything is ok before you start using it for important stuff.

Regards and best wishes,

Justin Clift