| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com> |
| Subject: | Re: Updating IPC::Run in CI? |
| Date: | 2025-09-22 22:35:22 |
| Message-ID: | CAOYmi+m8om5j=E6HpRdMfbGCmfnjL++OeC1FkrM=ZmF5EZ=H+w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 22, 2025 at 1:24 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> +1. Maybe we can stop doing this at some future time when all those
> OSes have absorbed an up-to-date IPC::Run, but for the near term we're
> merely exposing ourselves to known failures.
On Mon, Sep 22, 2025 at 1:27 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I think your position has merit. However, I'd like to have at least one of the
> tasks continue to use the non-built-in IPC::Run.
>
> I'll review patches installing a newer IPC::Run.
I will work on that, then. Thanks both!
> Seperately, I wonder if we ought to add a warning to configure/meson output
> about IPC::Run < 2025...
Probably. I imagine it's going to be very noisy for a bit, though.
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Chao Li | 2025-09-22 22:21:03 | Re: Fix wrong filename in header comment of gin_tuple.h |