| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Devrim Gündüz <devrim(at)gunduz(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
| Subject: | Re: LLVM 22 |
| Date: | 2026-04-02 04:26:42 |
| Message-ID: | 3191452.1775104002@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Thu, Apr 2, 2026 at 4:31 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Just out of curiosity: I see you back-patched that all the way,
>> but midge had only been failing on v18 and HEAD. Were you just
>> being defensive, or is there something deeper there?
> It was failing locally for me on all branches.
Ah, thanks for that detail.
> I don't know why midge wasn't failing on 14-17. Could jit be disabled
> somewhere secret? Aarch64 vs amd64, but this issue doesn't seem to be
> architecture related, it's IR-level.
Definitely not arch-specific, because I reproduced it on x86_64.
midge's lack of failure is odd then, but I'm not sure it's worth
expending a lot of brain cells on.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-04-02 05:01:37 | Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? |
| Previous Message | Tom Lane | 2026-04-02 04:22:48 | Re: Small and unlikely overflow hazard in bms_next_member() |