Re: installcheck-world concurrency issues
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org
Cc: Peter Geoghegan <pg@bowt.ie>
Date: 2022-10-05T06:16:37Z
Lists: pgsql-hackers
On 04.10.22 01:41, Andres Freund wrote: > BTW, shouldn't src/test/modules/unsafe_tests use the PG_TEST_EXTRA mechanism > somehow? Seems not great to run it as part of installcheck-world, if we don't > want to run it as part of installcheck. I think there are different levels and kinds of unsafeness. The ssl and kerberos tests start open server processes on your machine. The modules/unsafe_tests just make a mess of your postgres instance. The latter isn't a problem when run against a temp instance.
Commits
-
tests: Rename conflicting role names
- d90aa68c96a8 14.21 landed
- aa2ec0403d0a 15.16 landed
- 6a20b04f0408 16.0 landed
-
tests: Restrict pg_locks queries in advisory_locks.sql to current database
- 81487c83bed9 12.21 landed
- f232d7c6827c 13.17 landed
- e750e413325e 14.14 landed
- 3981fd5869fc 15.9 landed
- c3315a7da57b 16.0 landed