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 16525.1271730549@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?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Apr 19, 2010 at 9:51 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.

> Well, at this point the issue is deciding whether we're going to try
> to do anything about this before beta.

The reason it seems of concern for 9.0 is that now we have a custom
SUSET variable in plpgsql.  If we don't fix this then we need to think
hard about the alternative of forcing the variable into the core code
to avoid the gotchas.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: row estimation off the mark when generate_series calls are involved
Next
From: Robert Haas
Date:
Subject: Re: plpgsql GUC variable: custom or built-in?