Re: BUG #17415: Unable to use underscore as first character in set_config custom parameter - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17415: Unable to use underscore as first character in set_config custom parameter
Date
Msg-id 1012792.1645631940@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17415: Unable to use underscore as first character in set_config custom parameter  (Japin Li <japinli@hotmail.com>)
List pgsql-bugs
Japin Li <japinli@hotmail.com> writes:
> On Wed, 23 Feb 2022 at 16:36, PG Bug reporting form <noreply@postgresql.org> wrote:
>> SELECT set_config('_foo.bar', 'foo', FALSE);
>> ERROR:  invalid configuration parameter name "_foo.bar"
>> DETAIL:  Custom parameter names must be two or more simple identifiers
>> separated by dots.

> According to the comment of valid_custom_variable_name(), the custom variable
> must be two or more identifiers separated dots, and the identifier confirm
> scan.l, see below:
> However, the code in valid_custom_variable_name() doesn't confirm it.

Yeah, it's supposed to match scan.l, so that's an embarrassing
oversight.  Will apply patch.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
Next
From: Tom Lane
Date:
Subject: Re: BUG #17416: Server crashes due to python3 stack overflow on executing multiple plpy.rollback() calls