Hi, On Sat, Feb 17, 2024 at 09:54:22AM +0100, Clemens Eisserer wrote: > | can you try to upgrade and check whether your > | problamatic case is fixed as well? If not, I will reopen this bug > | report. > | are usually very bad memory leaks > | due to the way PostgreSQL uses LLVM. > > I've just tested the query with 15.6 - and the crash still occurs, > despite the closed bug report ;)
Ok, I have reopened it. > As can be seen in my email to the postgresql mailing list this is a > segfault crash, not some failed allocation or the linux oom killer > kicking in. > > Also the issue was analyzed by the postgresql devs and they came to > the conclusion it is a bug within llvm-14. > As mentioned, I've tested the same query on the same dataset with the > same version of postgresql (15.5) on the same hardware on ubuntu, with > the sole difference that ubuntu links to llvm-15 and there the query > succeeds and postgresql doesn't crash. If you want to stay on Debian, you can try the Postgres community repositories from apt.postgresql.org - the postgresql-15 packages for Debian 12 are linked against llvm16 it seems: https://wiki.postgresql.org/wiki/Apt https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15/postgresql-15_15.6-1.pgdg120%2B2_arm64.deb > Just to be curious, what was the rational behind linking against the > oldest available llvm version available in the debian repos (I saw 14, > 15 and 16 are provided). I don't know, but Debian will not switch LLVM versions in a stable release I believe, sorry. Michael
