Re: Making background psql nicer to use in tap tests

Mikael Kjellström <mikael.kjellstrom@gmail.com>

From: Mikael Kjellström <mikael.kjellstrom@gmail.com>

To: Daniel Gustafsson <daniel@yesql.se>, Tom Lane <tgl@sss.pgh.pa.us>

Cc: Andrew Dunstan <andrew@dunslane.net>, Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Melanie Plageman <melanieplageman@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>

Date: 2023-04-08T08:00:50Z

Lists: pgsql-hackers

On 2023-04-08 09:53, Daniel Gustafsson wrote:

>> I recommend
>> just setting up this one test to SKIP if IPC::Run is too old.
> 
> Yes, will do that when I have a little more time at hand for monitoring the BF
> later today.

So what do you want me to do about grison and morepork?  I guess I could 
try to install a newer version of IPC::Run from CPAN or should I just 
leave it be?

/Mikael

Commits

Fix missing installation/uninstallation rules for BackgroundPsql.pm
- 241ef53b6a95 12.20 landed
- 0d80e59a1b2c 13.16 landed
- 1185be355462 14.13 landed
- 9d7506a2f7cb 15.8 landed
Backport BackgroundPsql perl test module
- 4b467a6581af 12.20 landed
- 12f327b210b3 13.16 landed
- 31877cd8ec8c 14.13 landed
- d5fd7865f068 15.8 landed
- 187b8991f70f 16.4 landed
Add missing uninstallation rule for BackgroundPsql.pm
- 7039c7cff673 16.0 cited
Fix missing installation rules for BackgroundPsql.pm
- a4c17c86176c 16.0 cited
Skip \password TAP test on old IPC::Run versions
- 2e57ffe12f6b 16.0 landed
Test SCRAM iteration changes with psql \password
- bf5a894c5571 16.0 landed
Refactor background psql TAP functions
- 664d757531e1 16.0 landed