From: Tom Lane <tgl@sss.pgh.pa.us>
To: Japin Li <japinli@hotmail.com>
Cc: danielpolski@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17415: Unable to use underscore as first character in set_config custom parameter
Date: Wed, 23 Feb 2022 10:59:00 -0500
Message-ID: <1012792.1645631940@sss.pgh.pa.us> (raw)
In-Reply-To: <MEYP282MB166995C33420AB59FC285323B63C9@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM>
References: <17415-ebdb683d7e09a51c@postgresql.org>
<MEYP282MB166995C33420AB59FC285323B63C9@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, japinli@hotmail.com, danielpolski@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17415: Unable to use underscore as first character in set_config custom parameter
In-Reply-To: <1012792.1645631940@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox