| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Getting rid of regression test input/ and output/ files |
| Date: | 2021-12-20 04:51:29 |
| Message-ID: | CADkLM=eTApQKXA0mtrAMqzmeSPj0eKymryhdnz0oh-M0_=52MA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Dec 19, 2021 at 7:00 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Corey Huinker <corey(dot)huinker(at)gmail(dot)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
>
Fair enough.
Patches didn't apply with `git apply` but did fine with `patch -p1`, from
there it passes make check-world.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2021-12-20 04:53:00 | Re: row filtering for logical replication |
| Previous Message | Amit Kapila | 2021-12-20 04:08:36 | Re: parallel vacuum comments |