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

From: Greg Stark <stark(at)mit(dot)edu>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Getting rid of regression test input/ and output/ files
Date: 2021-12-21 04:58:07
Message-ID: CAM-w4HOmSBcxS4YqHPcHZZkMc-yQq_Fa6-6fdR3Qezv4TR4k0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 19 Dec 2021 at 18:41, Corey Huinker <corey(dot)huinker(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-12-21 05:04:06 Re: parallel vacuum comments
Previous Message Peter Geoghegan 2021-12-21 04:52:39 Re: do only critical work during single-user vacuum?