Re: RISC-V animals sporadically produce weird memory-related failures - Mailing list pgsql-hackers

From Tom Turelinckx
Subject Re: RISC-V animals sporadically produce weird memory-related failures
Date
Msg-id 75b3a85a-8b07-4722-9f4b-c332d2ddecb0@app.fastmail.com
Whole thread Raw
In response to Re: RISC-V animals sporadically produce weird memory-related failures  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: RISC-V animals sporadically produce weird memory-related failures
List pgsql-hackers
Hi Alexander,

On Mon, Dec 2, 2024, at 2:00 PM, Alexander Lakhin wrote:
> These crashes are hardly related to code changes, so maybe there are
> platform-specific issues still...

I naively assumed that because llvm and clang are available in Trixie on riscv64 that I could simply install them and
enable--with-llvm on copperhead, but I then discovered that this caused lots of segmentation faults and I had to revert
the--with-llvm again. Sorry about not first testing without submitting results.
 

> Unfortunately, the log files saved don't include coredump information,
> maybe because of inappropriate core_pattern.

I had increased the core file size limit in /etc/security/limits.conf, but in Trixie this is overruled by a default
/etc/security/limits.d/10-coredump-debian.conf.Moreover, the core_pattern was set by apport on the Ubuntu lxc host, but
apportis not available in the Trixie lxc guest. I have now corrected both issues, and a simple test resulted in a core
filebeing written to the current directory, like it was before the upgrade.
 

Best regards,
Tom



pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: Using read stream in autoprewarm
Next
From: Peter Geoghegan
Date:
Subject: Re: Incorrect result of bitmap heap scan.