Horton

Re: Possible regression setting GUCs on \connect

Alexander Korotkov <aekorotkov@gmail.com>

View thread View on postgr.es
From: Alexander Korotkov <aekorotkov@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: David Steele <david@pgmasters.net>, Tom Lane <tgl@sss.pgh.pa.us>, Alexander Korotkov <akorotkov@postgresql.org>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2023-04-27T19:20:13Z
Lists: pgsql-hackers 
.On Thu, Apr 27, 2023 at 9:55 PM Nathan Bossart
<nathandbossart@gmail.com> wrote:
> On Thu, Apr 27, 2023 at 09:53:23PM +0300, Alexander Korotkov wrote:
> > Thanks to everybody for catching and investigating this.
> > Nathan, I'd like to push it myself.  I'm also going to check the code
> > for similar errors.
>
> Sounds good!

I didn't find similar bugs in 096dd80f3c.  Pushed!

------
Regards,
Alexander Korotkov

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.