Re: Backporting BackgroundPsql

Heikki Linnakangas <hlinnaka@iki.fi>

From: Heikki Linnakangas <hlinnaka@iki.fi>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Daniel Gustafsson <daniel@yesql.se>
Cc: Andrew Dunstan <andrew@dunslane.net>, Andres Freund <andres@anarazel.de>, Melanie Plageman <melanieplageman@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Mikael Kjellström <mikael.kjellstrom@gmail.com>
Date: 2024-06-25T10:32:59Z
Lists: pgsql-hackers
On 25/06/2024 13:26, Heikki Linnakangas wrote:
> While fixing a recent bug on visibility on a standby [1], I wrote a 
> regression test that uses BackgroundPsql to run some queries in a 
> long-running psql session. The problem is that that was refactored in 
> v17, commit 664d757531. The test I wrote for v17 doesn't work as it is 
> on backbranches. Options:

Sorry, I meant v16. The BackgroundPsql refactorings went into v16. The 
backporting question remains for v15 and below.

-- 
Heikki Linnakangas
Neon (https://neon.tech)




Commits

  1. Fix missing installation/uninstallation rules for BackgroundPsql.pm

  2. Backport BackgroundPsql perl test module

  3. Add missing uninstallation rule for BackgroundPsql.pm

  4. Fix missing installation rules for BackgroundPsql.pm

  5. Skip \password TAP test on old IPC::Run versions

  6. Test SCRAM iteration changes with psql \password

  7. Refactor background psql TAP functions