| 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-29 08:57:28 |
| Message-ID: | alpine.DEB.2.20.1612290950590.4911@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Please, could you remove the part of the mail you are not responding to
and just keep the relevant part?
>> Whatever the features and syntax, you can always shoot yourself in the
>> foot.
>
> I disagree
Hmmm... I have succeeded in shotting myself in the foot with possibly
every feature of every language I have used. This is called experience...
in the end you do know how NOT to do things:-)
> - some concepts are more robust, other less.
Sure. The use-case under discussion is about ONE session variable holding
an expensive to compute security status which can be consulted by other
functions. I think that probably one can have it right with both
approaches, even if it is on the second try...
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-12-29 09:00:05 | Re: proposal: session server side variables |
| Previous Message | Craig Ringer | 2016-12-29 08:51:42 | Re: [PATCH] Fix minor race in commit_ts SLRU truncation vs lookups |