Re: simply custom variables protection

>"Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> writes:
> > this patch contains function ArmorCustomVariables. This function set
>flag
> > armored on any custom variable. From this moment only superuser can
>change
> > this variable.
>
>Why is this a good idea? Why don't you just fix the problem as
>previously agreed, namely make the GUC context values work properly
>for custom variables?
>

I am sorry, I don't see it. In my solution module knows own variables and
can chose what want to do with its. So if I like ro variables, then I add
into module init calling ResetPgVariables() and ArmorCustomVariables(), and
without anything the behave is same like current.What do you though.

Regards
Pavel Stehule

_________________________________________________________________
Chcete sdilet sve obrazky a hudbu s prateli? http://messenger.msn.cz/