| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | assam258(at)gmail(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org, jian(dot)universality(at)gmail(dot)com, zsolt(dot)parragi(at)percona(dot)com, sjjang112233(at)gmail(dot)com, vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl, jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com, peter(at)eisentraut(dot)org, li(dot)evan(dot)chao(at)gmail(dot)com |
| Subject: | Re: Row pattern recognition |
| Date: | 2026-06-22 12:55:36 |
| Message-ID: | 20260622.215536.1729984032454200237.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Henson,
> Before the patch list, a note on CI: cfbot has been red here, but the
> failure is not RPR -- it is the libLLVM 19 + ASAN JIT crash (CF 6870), which
> reproduces on plain master. The build-system fix (exclude sanitizer flags
> from JIT bitcode generation) is Matheus Alcantara's; the meson half is
> v3-0001-Exclude-sanitizer-flags-from-LLVM-JIT-bitcode-gen.patch:
>
>
> https://postgr.es/m/CAAAe_zBX5uV9K0ikuROLgdNvDCgGqHRskT-73L+oX9=3aXR2AQ@mail.gmail.com
>
> For v50, what would you think about folding that meson patch in as a
> temporary prerequisite at the front of the series, so cfbot's ASAN build
> gets past the JIT crash and actually exercises RPR?
I have sent an email to those who are working on CI to let them know
the CI is partly broken and the fix has been proposed.
https://www.postgresql.org/message-id/20260622.192319.148395607405547262.ishii%40postgresql.org
Once the fix is installed, the patch does not need to be part of
v50. Let's wait for a while.
Regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shinya Kato | 2026-06-22 13:00:58 | Fix contradictory comment for pgstat_slru_flush_cb() |
| Previous Message | Matthias van de Meent | 2026-06-22 12:50:34 | [WIP] Adding a { LOCK ROWS | LOCK KEY INDEX } clause to FK definitions |