| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Tristan Partin <tristan(at)partin(dot)io>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: PG_TEST_EXTRA and meson |
| Date: | 2024-08-11 12:53:31 |
| Message-ID: | 5d9ce30a-a088-427a-a863-afa128c73d7e@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2024-08-09 Fr 5:26 AM, Ashutosh Bapat wrote:
> I this the patch lacks overriding PG_TEST_EXTRA at run time.
>
> AFAIU, following was expected behaviour from both meson and make.
> Please correct if I am wrong.
> 1. If PG_TEST_EXTRA is set at the setup/configuration time, it is not
> required to be set at run time.
> 2. Runtime PG_TEST_EXTRA always overrides configure time PG_TEST_EXTRA.
Yes, that's my understanding of the requirement.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ayush Vatsa | 2024-08-11 13:34:41 | Re: Restricting Direct Access to a C Function in PostgreSQL |
| Previous Message | Pavel Stehule | 2024-08-11 12:11:59 | Re: Restricting Direct Access to a C Function in PostgreSQL |