| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Fabrízio de Royes Mello <fabriziomello(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:38:39 |
| Message-ID: | alpine.DEB.2.20.1612281531390.4911@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> For security the variable should be persistent.
Why should they? If it is a session variable, being created when needed or
used with the right type could be enough?
> If you would to do statical analyse (what you usually would), then variable
> should be persistent.
I do not understand what static analysis you would need/want to do on
session variables.
> Currently the big issue of plpgsql_check is work with temporary tables.
Do you mean that temporary table are too slow/costly?
> Local objects or dynamic sql is stop for static check.
Hmm. If something is dynamic, it is not static, but I do not understand
your point.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-12-28 14:53:58 | Re: make more use of RoleSpec struct |
| Previous Message | Fabien COELHO | 2016-12-28 14:31:27 | Re: proposal: session server side variables |