| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: regression tests fails with llvm22 |
| Date: | 2026-03-04 04:02:01 |
| Message-ID: | CAFj8pRCe3-D7nG3cqVxLX6R2Duhq1EMXey0-QNt2bQ+WC3pnUA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
út 3. 3. 2026 v 12:33 odesílatel Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
napsal:
> On 03/03/26 02:06, Pavel Stehule wrote:
> > Hi
> >
> > I did upgrade today
> >
> > pavel(at)nemesis:~/src/postgresql$ uname -a
> > Linux nemesis 6.19.5-300.fc44.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Feb 28
> > 00:00:53 UTC 2026 x86_64 GNU/Linux
> >
> > pavel(at)nemesis:~/src/postgresql$ llvm-config --version
> > 22.1.0
> >
> > and regression tests fails
> >
> > cat
> > /home/pavel/src/postgresql/src/test/isolation/output_iso/regression.diffs
> > diff -U3
> >
> /home/pavel/src/postgresql/src/test/isolation/expected/multixact-stats.out
> >
> /home/pavel/src/postgresql/src/test/isolation/output_iso/results/multixact-stats.out
> > ---
> >
> /home/pavel/src/postgresql/src/test/isolation/expected/multixact-stats.out
> > 2026-02-19 05:31:42.337867043 +0100
> > +++
> >
> /home/pavel/src/postgresql/src/test/isolation/output_iso/results/multixact-stats.out
> > 2026-03-03 06:00:45.850492589 +0100
> > @@ -68,22 +68,11 @@
> > ]
> > ) AS r(assertion, ok);
> >
> > -assertion |ok
> > -------------------------+--
> > -is_init_mxids |t
> > -is_init_members |t
> > -is_init_oldest_mxid |t
> > -is_init_oldest_off |t
> > -is_oldest_mxid_nondec_01|t
> > -is_oldest_mxid_nondec_12|t
> > -is_oldest_off_nondec_01 |t
> > -is_oldest_off_nondec_12 |t
> > -is_members_increased_ge1|t
> > -is_mxids_nondec_01 |t
> > -is_mxids_nondec_12 |
> > -is_members_nondec_01 |
> > -is_members_nondec_12 |
> > -(13 rows)
> > +FATAL: fatal llvm error: Broken module found, compilation aborted!
> > +server closed the connection unexpectedly
> > + This probably means the server terminated abnormally
> > + before or while processing the request.
> >
> > step s1_commit: COMMIT;
> > -step s2_commit: COMMIT;
> > +failed to send query for step s2_commit: no connection to the server
> > +
> >
>
> I think that [1] is about to fix this.
>
> [1]
>
> https://www.postgresql.org/message-id/CA%2BhUKGJTumad75o8Zao-LFseEbt%3DenbUFCM7LZVV%3Dc8yg2i7dg%40mail.gmail.com
yes - it is. This issue is not closed yet
Regards
Pavel
>
>
> --
> Matheus Alcantara
> EDB: https://www.enterprisedb.com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-03-04 04:06:18 | pgsql: Change default value of default_toast_compression to "lz4", when |
| Previous Message | Robert Haas | 2026-03-04 03:36:13 | Re: pg_plan_advice (now with transparent SQL plan performance overrides - pg_stash_advice) |