From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-16 09:25:25 |
Message-ID: | 7ECCA246-B56F-48A6-853D-05C58F7D12DA@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 15 Feb 2024, at 16:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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
Doh, I missed that when looking.
>> 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;
Right, I was mostly thinking of a chapter along the lines of "I am an extension
author, what features does this tool have to help me write good tests".
> the complete lack of equivalent info about what
> to do in a meson build clearly needs to be rectified.
Indeed.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Luzanov | 2024-02-16 10:00:53 | Show password presence in pg_roles for authorized roles |
Previous Message | Shubham Khanna | 2024-02-16 09:20:05 | Re: speed up a logical replica setup |