From: | Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Maxim Orlov <orlovmg(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Use "?=" operator for a contrib makefile in documentation |
Date: | 2025-10-02 05:39:02 |
Message-ID: | 4ad6176c1cf2a464a8af932e87b4f6e0@postgrespro.ru |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello!
We use common scripts to check various PostgreSQL modules with various
PostgreSQL major versions. It is easier to set the required PG_CONFIG in
the enviroment than to change various make commands. In particular, they
are quite common if we want to build, install or run installcheck in a
specific directory. The PATH enviroment variable also works, but
PG_CONFIG is usually sufficient and we want to be sure of that.
On 2025-09-29 15:50, Peter Eisentraut wrote:
> I think the current text is preferable. This allows running
>
> make PG_CONFIG=...
>
> so that you can pick a different PostgreSQL installation for a
> particular build.
>
> If you always want to use a particular PostgreSQL installation, then
> you could alter the PATH in the environment.
>
> I don't know that there is a use case of setting only PG_CONFIG in the
> environment that is not covered by these other two approaches.
--
Marina Polyakova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2025-10-02 05:44:21 | Re: GB18030-2022 Support in PostgreSQL |
Previous Message | John Naylor | 2025-10-02 05:25:59 | Re: Proposal for enabling auto-vectorization for checksum calculations |