From: | Justin Clift <justin(at)postgresql(dot)org> |
---|---|
To: | jack <jack4pg(at)a7q(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: constant crashing hardware issue and thank you TAKE AWAY |
Date: | 2024-04-17 16:19:17 |
Message-ID: | f18ca15e73ea07a8b196a1e6cc04bcd6@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Johnathan Tiamoh | 2024-04-17 17:13:09 | Performance degradation after upgrading from 9.5 to 14 |
Previous Message | Sasmit Utkarsh | 2024-04-17 15:37:16 | Re: Assistance needed for the query execution in non-public schema |