Re: [HACKERS] proposal: session server side variables - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] proposal: session server side variables
Date
Msg-id alpine.DEB.2.20.1612290950590.4911@lancre
Whole thread Raw
In response to Re: [HACKERS] proposal: session server side variables  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] proposal: session server side variables
List 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.



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] [PATCH] Fix minor race in commit_ts SLRU truncation vs lookups
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] proposal: session server side variables