Re: proposal: schema PL session variables - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: schema PL session variables
Date
Msg-id CAFj8pRBK3fmOEP74Xbn2GN_2bH6zw3VNWggLww7v1wsNK98BvQ@mail.gmail.com
Whole thread Raw
In response to Re: proposal: schema PL session variables  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers


2016-02-12 22:41 GMT+01:00 Jim Nasby <Jim.Nasby@bluetreble.com>:
On 2/12/16 2:58 PM, Pavel Stehule wrote:
I think that's probably true, but this also shows why we need to consider different PLs too. As it stands right now, the only way to access a variable outside of plpgsql would be to call a plpgsql function, and currently there's no way to make a plpgsql function private. So for this to work, private variables probably need to be exposed directly through the pl handler.


Again, I'm not saying this all has to be implemented up front, but there needs to be a plan for how it would work.

I think it would be a good idea to start a wiki page on this topic to start collecting stuff together.

I'll do it. Thank you for comments

Regards

Pavel
 

--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [COMMITTERS] pgsql: Code cleanup in the wake of recent LWLock refactoring.
Next
From: Michael Paquier
Date:
Subject: Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby