From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Oleg Bartunov <obartunov(at)gmail(dot)com> |
Subject: | Re: proposal: schema PL session variables |
Date: | 2016-02-08 13:30:38 |
Message-ID: | 56B8987E.1000307@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 02/08/2016 03:16 AM, Pavel Stehule wrote:
> Hi
>
> On Russian PgConf I had a talk with Oleg about missing features in
> PLpgSQL, that can complicates a migrations from Oracle to PostgreSQL.
> Currently I see only one blocker - missing protected session
> variables. PL/SQL has package variables with possible only package
> scope and session life cycle. Currently we cannot to ensure/enforce
> schema scope visibility - and we cannot to implement this
> functionality in PL languages other than C.
>
> I propose really basic functionality, that can be enhanced in future -
> step by step. This proposal doesn't contain any controversial feature
> or syntax, I hope. It is related to PLpgSQL only, but described
> feature can be used from any PL languages with implemented interface.
I think it would make sense to implement the interface in at least one
of our other supported PLs. I'm not entirely clear how well this will
match up with, say, plperl, but I'd be interested to see.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2016-02-08 13:41:56 | Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs) |
Previous Message | Pavel Stehule | 2016-02-08 13:16:30 | Re: proposal: schema PL session variables |