Re: Augment every test postgresql.conf
Noah Misch <noah@leadboat.com>
From: Noah Misch <noah@leadboat.com>
To: pgsql-hackers@postgresql.org
Date: 2018-12-30T02:40:14Z
Lists: pgsql-hackers
Attachments
- TEMP_CONFIG-tap-v1.patch (text/x-diff) patch v1
On Fri, Dec 28, 2018 at 06:19:50PM -0800, Noah Misch wrote: > "env EXTRA_REGRESS_OPTS=--temp-config=SOMEFILE make check" appends the > contents of SOMEFILE to the test cluster's postgresql.conf. I want a similar > feature for TAP suites and other non-pg_regress suites. (My immediate use > case is to raise authentication_timeout and wal_sender_timeout on my buildfarm > animals, which sometimes fail at the defaults.) I'm thinking to do this by > recognizing the PG_TEST_TEMP_CONFIG environment variable as a > whitespace-separated list of file names for appending to postgresql.conf. Looking more closely, we already have the TEMP_CONFIG variable and apply it to everything except TAP suites. Closing that gap, as attached, is enough. The buildfarm client uses TEMP_CONFIG to implement its extra_config setting, so this will cause extra_config to start applying to TAP suites.
Commits
-
Fail pgwin32_message_to_UTF16() for SQL_ASCII messages.
- 08e3fd96f70a 9.4.23 landed
- 9dc65bcf9dec 9.5.18 landed
- ff7555c4f13a 9.6.14 landed
- 4ec14e5aa1f7 11.4 landed
- 409f5303ced6 10.9 landed
- d02768ddd179 12.0 landed
-
Honor TEMP_CONFIG in TAP suites.
- 8dab099bb49c 9.6.14 landed
- 7a6a541234fd 10.9 landed
- 239dcf8f15b7 11.4 landed
- 54c2ecb56707 12.0 landed
-
Respect TEMP_CONFIG when pg_regress_check and friends are called
- 87cc6b57a911 9.6.0 cited