Re: fix: propagate M4 env variable to flex subprocess

From: "J(dot) Javier Maestro" <jjmaestro(at)ieee(dot)org>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: fix: propagate M4 env variable to flex subprocess
Date: 2025-06-22 23:34:20
Message-ID: CABvji05kQStwH56_HZXsoQf+9MZnC0Ktgy8efKAphapgfAPFFA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 17, 2025 at 6:15 AM Peter Eisentraut <peter(at)eisentraut(dot)org>
wrote:

> This patch looks right to me.
>

Great, thanks!

I would wait for the PG19 branching at this point, unless there is a
> concrete need for backpatching.

This patch fixes just one of the issues I found when trying to have a
reproducible PG build... and, given the fact that there are still other
issues that make a PG build non-reproducible (see the other patches in
https://github.com/monogres/postgres/compare/REL_16_0...monogres/patches/16.0)
I'd say it's OK if it's not backported.

Thank you!

Javier

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message J. Javier Maestro 2025-06-22 23:35:18 Re: fix: propagate M4 env variable to flex subprocess
Previous Message Paul A Jungwirth 2025-06-22 23:19:20 Re: SQL:2011 Application Time Update & Delete