From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: psql doesn't pass on exported shell environment functions |
Date: | 2017-07-07 16:00:12 |
Message-ID: | CAKFQuwac9cpa6U_jR4qdUzm_Z+SK5vj6jNS2NM2Vu=R57898=w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jul 7, 2017 at 8:45 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > I'm using Ubuntu 16.04
>
> Hmph. Works for me on RHEL6. I'm betting that Ubuntu has put in some
> weird security restriction, possibly an overreaction to the "shellshock"
> bug which was in the exported-functions feature.
>
Thank you both for looking at this. While my curiosity is still piqued
I've solved the original problem without resorting to exporting a function
through a psql invocation. Fortunately, exported functions are still seen
by directly called bash scripts so a few other areas where I leverage that
feature are still working.
I've haven't totally discounted local configuration interplay here - my
bashrc is non-trivial and there a few differences between the setups
besides versions - though a security enhancement in 16.04 seems plausible.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Mayank Agrawal | 2017-07-07 17:48:24 | Re: (Might be a bug) locale issue while upgrading data directory from PostgreSQL 8.4 to 9.5 |
Previous Message | Tom Lane | 2017-07-07 15:45:02 | Re: psql doesn't pass on exported shell environment functions |