Re: Making background psql nicer to use in tap tests

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Andres Freund <andres@anarazel.de>

Cc: pgsql-hackers@postgresql.org, Melanie Plageman <melanieplageman@gmail.com>

Date: 2023-01-30T20:06:46Z

Lists: pgsql-hackers

Andres Freund <andres@anarazel.de> writes:
> It's annoyingly hard to wait for the result of a query in a generic way with
> background_psql(), and more generally for psql. background_psql() uses -XAtq,
> which means that we'll not get "status" output (like "BEGIN" or "(1 row)"),
> and that queries not returning anything are completely invisible.

Yeah, the empty-query-result problem was giving me fits recently.
+1 for wrapping this into something more convenient to use.

			regards, tom lane

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