Horton

Re: Getting rid of regression test input/ and output/ files

Greg Stark <stark@mit.edu>

View thread View on postgr.es
From: Greg Stark <stark@mit.edu>
To: Corey Huinker <corey.huinker@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-12-21T04:58:07Z
Lists: pgsql-hackers 
On Sun, 19 Dec 2021 at 18:41, Corey Huinker <corey.huinker@gmail.com> wrote:
>
> 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]

Oof. That gives me the security heebie jeebies. Off the top of my head
PHP, CGI, SSH have all dealt with vulnerabilities caused by
accidentally importing variables they didn't intend to.

-- 
greg

Commits

  1. Merge dblink's paths test script into its main test.

  2. Remove dynamic translation of regression test scripts, step 2.

  3. Remove dynamic translation of regression test scripts, step 1.

  4. Add a \getenv command to psql.