Re: Allow passing extra options to initdb for tests
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter@eisentraut.org>,
Ian Lawrence Barwick <barwick@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2024-02-16T09:25:25Z
Lists: pgsql-hackers
> On 15 Feb 2024, at 16:21, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Daniel Gustafsson <daniel@yesql.se> writes: >> On 15 Feb 2024, at 11:38, Peter Eisentraut <peter@eisentraut.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
Commits
-
Allow passing extra options to initdb for tests
- 995d400ceca3 17.0 landed