| From: | "Peter 'PMc' Much" <pmc(at)citylink(dot)dinoex(dot)sub(dot)org> |
|---|---|
| To: | Tomas Vondra <tomas(at)vondra(dot)me> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Need help debugging SIGBUS crashes |
| Date: | 2026-03-17 15:31:08 |
| Message-ID: | ablzvEbITB73W0yY@disp.intra.daemon.contact |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 17, 2026 at 02:54:29PM +0100, Tomas Vondra wrote:
!
! BTW the first thing I'd try is testing memory with memtest86+ or a
! similar tool. I don't know what hardware you're using, but I recently
! dealt with weird failures on older machines, and it turned out to be
! faulty RAM modules.
Yes, I considered this as one of the first things, and then ruled
it out, because
A) this is a Haswell-Xeon EP, and not only does it have ECC, but I
have already seen it identify a bad stick on this very hardware,
B) given that we have address space randomization, and that the
postgres memory footprint is kept rather small here (it should
then use ZFS ARC), I consider it highly unlikely that a memory
defect would always hit at the very same code-line, and never
anywhere else or in a different program.
PMc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2026-03-17 15:32:02 | Re: finish TODOs in to_json_is_immutable, to_jsonb_is_immutable also add tests on it |
| Previous Message | Peter 'PMc' Much | 2026-03-17 15:29:14 | Re: Need help debugging SIGBUS crashes |