Re: Possible regression setting GUCs on \connect

David Steele <david@pgmasters.net>

From: David Steele <david@pgmasters.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alexander Korotkov <akorotkov@postgresql.org>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2023-04-27T18:28:26Z
Lists: pgsql-hackers
On 4/27/23 21:16, Tom Lane wrote:
> David Steele <david@pgmasters.net> writes:
>> Seems plausible. This can be reproduced by cloning [1] into contrib and
>> running `make check`. I can work out another test case but it may not
>> end up being simpler.
>> [1] https://github.com/pgaudit/pgaudit/tree/dev-pg16-ci
> 
> I tried to replicate this per that recipe, but it works for me:
> 
> $ git clone https://github.com/pgaudit/pgaudit.git pgaudit
> $ cd pgaudit
> $ git checkout dev-pg16-ci
> $ make -s check
> # +++ regress check in contrib/pgaudit +++
> # using temp instance on port 61696 with PID 1191703
> ok 1         - pgaudit                                   310 ms
> 1..1
> # All 1 tests passed.

I included the errors in the expect log so I could link to them. So test 
success means the error is happening.

> Note that I had to add
> 
> $ diff -pud Makefile~ Makefile
> --- Makefile~   2023-04-27 14:02:19.041714415 -0400
> +++ Makefile    2023-04-27 14:07:10.056909016 -0400
> @@ -20,3 +20,5 @@ top_builddir = ../..
>   include $(top_builddir)/src/Makefile.global
>   include $(top_srcdir)/contrib/contrib-global.mk
>   endif
> +
> +EXTRA_INSTALL += contrib/pg_stat_statements

Yeah, I rarely run tests in-tree, but I'll add this if it does not break 
our regular CI.

-David



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.