From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Allow passing extra options to initdb for tests |
Date: | 2024-02-15 15:21:35 |
Message-ID: | 3243768.1708010495@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> On 15 Feb 2024, at 11:38, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>> We don't have a man page for pg_regress, so there is no place to comprehensively document all the options and their interactions.
> This comes up every now and again, just yesterday there was a question on
> -general [0] about alternate output files which also are
> undocumented.
Really?
https://www.postgresql.org/docs/devel/regress-variant.html
> Maybe it's time to add documentation for pg_regress?
I'm inclined to think that a formal man page wouldn't be that useful,
since nobody ever invokes pg_regress directly; as Peter says, what
is of interest is the "make check" targets and the corresponding meson
behaviors. I think 32.1 is already reasonably thorough about the
make targets; but the complete lack of equivalent info about what
to do in a meson build clearly needs to be rectified.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2024-02-15 15:49:45 | Re: Replace current implementations in crypt() and gen_salt() to OpenSSL |
Previous Message | Matthias van de Meent | 2024-02-15 14:37:53 | Re: Reducing output size of nodeToString |