Re: [patch] \g with multiple result sets and \watch with copy queries
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Daniel Verite" <daniel@manitou-mail.org>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2022-10-04T13:08:44Z
Lists: pgsql-hackers
"Daniel Verite" <daniel@manitou-mail.org> writes: > Tom Lane wrote: >> Given the time pressure, I did not worry about installing regression >> test coverage for this stuff, but I wonder if we shouldn't add some. > Currently, test/regress/sql/psql.sql doesn't AFAICS write anything > outside of stdout, but \g, \o, \copy need to write to external > files to be tested properly. Yeah, I don't think we can usefully test these in psql.sql, because file-system side effects are bad in that context. But maybe a TAP test could cope? regards, tom lane
Commits
-
Fix psql's behavior with \g for a multiple-command string.
- 4a79fd1a754e 16.0 landed
- 595580aa1243 15.0 landed
-
Remove dynamic translation of regression test scripts, step 1.
- d1029bb5a26c 15.0 cited