Re: [GENERAL] psql doesn't pass on exported shell environment functions - Mailing list pgsql-general

From David G. Johnston
Subject Re: [GENERAL] psql doesn't pass on exported shell environment functions
Date
Msg-id CAKFQuwac9cpa6U_jR4qdUzm_Z+SK5vj6jNS2NM2Vu=R57898=w@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] psql doesn't pass on exported shell environment functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Fri, Jul 7, 2017 at 8:45 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.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.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] psql doesn't pass on exported shell environment functions
Next
From: Mayank Agrawal
Date:
Subject: Re: [GENERAL] (Might be a bug) locale issue while upgrading datadirectory from PostgreSQL 8.4 to 9.5