Date: Tue, 17 Mar 2026 16:31:08 +0100
From: "Peter 'PMc' Much" <pmc@citylink.dinoex.sub.org>
To: Tomas Vondra <tomas@vondra.me>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Need help debugging SIGBUS crashes
Message-ID: <ablzvEbITB73W0yY@disp.intra.daemon.contact>
References: <ablGaVLQ3N9WsHcc@disp.intra.daemon.contact>
 <33d99d2f-4020-4615-9314-2f1a19927fa6@vondra.me>
 <6dc6f9ba-27dc-492d-9f77-34792929a944@vondra.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6dc6f9ba-27dc-492d-9f77-34792929a944@vondra.me>
Archived-At: 
 <https://www.postgresql.org/message-id/ablzvEbITB73W0yY%40disp.intra.daemon.contact>
Precedence: bulk

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