pgsql: Re-allow custom GUC names that have more than two components.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Re-allow custom GUC names that have more than two components.
Date: 2021-06-02 22:50:34
Message-ID: E1loZh4-0002Gj-41@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Re-allow custom GUC names that have more than two components.

Commit 3db826bd5 disallowed this case, but it turns out that some
people are depending on it. Since the core grammar has allowed
it since 3dc37cd8d, it seems like this code should fall in line.

Per bug #17045 from Robert Sosinski.

Discussion: https://postgr.es/m/17045-6a4a9f0d1513f72b@postgresql.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/2955c2be79b35fa369c83fa3b5f44661cb88afa9

Modified Files
--------------
src/backend/utils/misc/guc.c | 15 ++++++++-------
src/test/regress/expected/guc.out | 20 ++++++++++++++++++--
src/test/regress/sql/guc.sql | 5 +++++
3 files changed, 31 insertions(+), 9 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2021-06-03 02:52:43 pgsql: Ignore more environment variables in TAP tests
Previous Message Tomas Vondra 2021-06-02 22:47:32 pgsql: Revert most of 39b66a91bd