| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: session server side variables |
| Date: | 2016-12-28 14:00:42 |
| Message-ID: | CAMsr+YGy-pPdsG04yiJ1H=L7qL=kiExn7L_UUZuncrbPKUzg6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28 December 2016 at 21:19, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
> Also, I'm not yet convinced that simple privatizable transcient/session
> variables would not be enough to fit the use case, so that for the same
> price there would be session variables for all, not only special ones with
> permissions.
Since, unlike Oracle, we don't have compiled packages or plan-caching
above the session level, there's not the same hard requirement for the
variable definition to be persistent.
So... maybe? The main question then becomes how you integrate access control.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-12-28 14:01:01 | Re: proposal: session server side variables |
| Previous Message | Ashutosh Bapat | 2016-12-28 13:29:32 | Re: Reporting planning time with EXPLAIN |