Re: Getting rid of regression test input/ and output/ files
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Corey Huinker <corey.huinker@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2021-12-20T00:00:26Z
Lists: pgsql-hackers
Corey Huinker <corey.huinker@gmail.com> writes: > Which brings up a tangential question, is there value in having something > that brings in one or more env vars as psql vars directly. I'm thinking > something like: > \importenv pattern [prefix] Meh ... considering we've gone this long without any getenv capability in psql at all, that seems pretty premature. regards, tom lane
Commits
-
Merge dblink's paths test script into its main test.
- 0e6e7f0806b2 15.0 landed
-
Remove dynamic translation of regression test scripts, step 2.
- dc9c3b0ff214 15.0 landed
-
Remove dynamic translation of regression test scripts, step 1.
- d1029bb5a26c 15.0 landed
-
Add a \getenv command to psql.
- 33d3eeadb21d 15.0 landed