Re: BUG #17237: set_config: Custom parameter names must be two or more simple identifiers separated by dots.

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: stepaunov(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17237: set_config: Custom parameter names must be two or more simple identifiers separated by dots.
Date: 2021-10-19 08:20:45
Message-ID: 5b85039e-99da-5a8f-a42c-59e5660f60f2@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 10/19/21 9:41 AM, PG Bug reporting form wrote:
>
> Our app uses guids as first part of set_config parameter name.
>
> On PostgreSQL 14.0 this script results in an error:
> SELECT set_config('182e33e7-12ff-4c4f-bc6e-0822e72fa7a4.param1'
> ,'test',true);
>
> Exception:
> [42602] ERROR: invalid configuration parameter name
> "182e33e7-12ff-4c4f-bc6e-0822e72fa7a4.param1"
> Custom parameter names must be two or more simple identifiers separated by
> dots.

This is not a bug but a deliberate change. It is mentioned in the
release notes (https://www.postgresql.org/docs/14/release-14.html) as a
backwards-incompatible change.
--
Vik Fearing

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Korotkov 2021-10-19 11:17:15 Re: BUG #17229: Segmentation Fault after upgrading to version 13
Previous Message PG Bug reporting form 2021-10-19 07:41:49 BUG #17237: set_config: Custom parameter names must be two or more simple identifiers separated by dots.