Re: Possible regression setting GUCs on \connect

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.

This is at commit 6f879bddbdcfbf9995ecee1db9a587e06027bd13 on
your dev-pg16-ci branch and df38157d94662a64e2f83aa8a0110fd1ee7c4776
on PG master.  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

else I got failures about pg_stat_statements not being installed.
But I don't see the failure you're complaining of.

			regards, tom lane