| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Explicitly enable meson features in CI |
| Date: | 2025-07-10 21:42:16 |
| Message-ID: | F24C7F1A-A99F-40A5-B7FF-3195FB3B2D09@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 10 Jul 2025, at 19:12, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> On Thu, Jul 10, 2025 at 2:59 AM Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
>> so it would be easier to catch if
>> one of the features is disabled without anyone noticing.
>
> Seems reasonable.
Agreed.
> If we do this, can we rename the job with a "- Meson
> Auto" suffix or something, to try to call the difference out
> explicitly?
+1
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-07-10 21:42:23 | Re: Horribly slow pg_upgrade performance with many Large Objects |
| Previous Message | Sami Imseih | 2025-07-10 21:34:34 | Re: Improve LWLock tranche name visibility across backends |