Re: plpgsql GUC variable: custom or built-in? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plpgsql GUC variable: custom or built-in?
Date
Msg-id 15488.1271728276@sss.pgh.pa.us
Whole thread Raw
In response to Re: plpgsql GUC variable: custom or built-in?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: plpgsql GUC variable: custom or built-in?
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> This thread is still on the open items list, as:
> Improve behavior of SUSET GUC variables added by loadable modules?
> Is there something that needs to be done here?  If so, what is it?

Well, if we knew exactly what to do, it wouldn't still be on the list.
The problem is that making a "custom" variable SUSET doesn't really
work: the system will not accept a value that's assigned before the
loadable module is loaded, even if it was assigned by a superuser.
I suggested a fix in the referenced thread, but it's not exactly an
ideal fix.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: shared_buffers documentation
Next
From: Robert Haas
Date:
Subject: Re: plpgsql GUC variable: custom or built-in?