"Pavel Stehule" <[EMAIL PROTECTED]> 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?

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to