Horton

Re: Possible regression setting GUCs on \connect

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: Pavel Borisov <pashkin.elfe@gmail.com>, Alexander Korotkov <aekorotkov@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Nathan Bossart <nathandbossart@gmail.com>, David Steele <david@pgmasters.net>, Pg Hackers <pgsql-hackers@postgresql.org>, rmt@lists.postgresql.org
Date: 2023-05-17T06:17:13Z
Lists: pgsql-hackers 
On Sun, Apr 30, 2023 at 12:25:20PM -0400, Jonathan S. Katz wrote:
> [RMT hat]
> 
> I read through the original thread[1] to understand the use case and also
> the concerns, but I need to study [1] and this thread a bit more before I
> can form an opinion.
> 
> The argument that there is "demand from users" is certainly one I relate to,
> but there have been high-demand features in the past (e.g. MERGE, SQL/JSON)
> that have been reverted and released later due to various concerns around
> implementation, etc. The main job of the RMT is to ensure a major release is
> on time and is as stable as possible, which will be a major factor into any
> decisions if there is lack of community consensus on an open item.

(note: Not RMT this year)

This thread had no replies for the last two weeks, and beta1 is
planned for next week.  Alexander, what are your plans here?
--
Michael

Commits

  1. Revert "Add USER SET parameter values for pg_db_role_setting"

  2. Fix wrong construct_array_builtin() call in GUCArrayDelete()

  3. In hstore_plpython, avoid crashing when return value isn't a mapping.

  4. Allow granting SET and ALTER SYSTEM privileges on GUC parameters.