| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andreas Karlsson <andreas(at)proxel(dot)se> |
| Cc: | Rustam ALLAKOV <rustamallakov(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Add support for EXTRA_REGRESS_OPTS for meson |
| Date: | 2026-03-31 10:46:35 |
| Message-ID: | acumC5qBYIYNRF8U@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 31, 2026 at 10:45:32AM +0200, Andreas Karlsson wrote:
> Agreed, the question is just where we should document them.
>
> I would say one of these two pages:
>
> https://www.postgresql.org/docs/current/install-meson.html
> https://www.postgresql.org/docs/current/regress-run.html
regress-run would be a nicer fit in the long run, where it seems to me
that the existing documentation is wrong with its decision to document
the regression tests that can be run in meson in a section for the
build and install:
https://www.postgresql.org/docs/current/install-meson.html#INSTALL-PROCEDURE-MESON
The format that we use for the coverage code is something I find
pretty clear:
https://www.postgresql.org/docs/current/regress-coverage.html
We have two sub-sections, one for configure/make and one meson, which
is nice. Perhaps we don't need to have new sub-sections, limiting
ourselves to mention some of the equivalents that can be used with
meson?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2026-03-31 10:47:18 | Re: Adding REPACK [concurrently] |
| Previous Message | Bertrand Drouvot | 2026-03-31 10:45:50 | Re: relfilenode statistics |