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-27T18:53:23Z
Lists: pgsql-hackers 
Hi!

On Thu, Apr 27, 2023 at 9:51 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
> On Thu, Apr 27, 2023 at 09:47:33PM +0300, David Steele wrote:
> > That seems to work. The errors are now gone.
>
> Great.  Barring objections, I'll plan on committing this shortly.

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.

------
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.