Re: simply custom variables protection - Mailing list pgsql-patches

From Tom Lane
Subject Re: simply custom variables protection
Date
Msg-id 7715.1173568092@sss.pgh.pa.us
Whole thread Raw
In response to simply custom variables protection  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
Responses Re: simply custom variables protection  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
List pgsql-patches
"Pavel Stehule" <pavel.stehule@hotmail.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?

            regards, tom lane

pgsql-patches by date:

Previous
From: Joachim Wieland
Date:
Subject: Re: guc patch: Make variables fall back to default values
Next
From: Tom Lane
Date:
Subject: WIP patch for plan invalidation