Re: Extending USE_MODULE_DB to more test suite types
Noah Misch <noah@leadboat.com>
From: Noah Misch <noah@leadboat.com>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2019-04-04T05:56:58Z
Lists: pgsql-hackers
On Mon, Apr 01, 2019 at 01:01:11PM -0400, Andrew Dunstan wrote: > On Mon, Apr 1, 2019 at 9:52 AM Noah Misch <noah@leadboat.com> wrote: > > I plan to back-patch the PostgreSQL patch, to combat buildfarm noise. Perhaps > > someone has test automation that sets USE_MODULE_DB and nonetheless probes the > > exact database name "pl_regression", but I'm not too worried. The original > > rationale for USE_MODULE_DB, in commit ad69bd0, was to facilitate pg_upgrade > > testing. Folks using "make installcheck-world" to populate a cluster for > > pg_upgrade testing will see additional test coverage, which may cause > > additional failures. I'm fine with that, too. Pushed. It looks like XversionUpgradeSave relies on having a "contrib_regression" database: https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=crake&br=REL9_5_STABLE > Excellent. Extending use of USE_MODULE_DB has been on my list of > things to do. I'll add the buildfarm patch right away. It should be > harmless before these changes are made. Thanks.
Commits
-
Handle USE_MODULE_DB for all tests able to use an installed postmaster.
- 624edab58288 9.4.22 landed
- 267d83c7d7d2 9.5.17 landed
- 991a9125351c 9.6.13 landed
- 8541304d5c77 10.8 landed
- 426d93d24429 11.3 landed
- f433394e48af 12.0 landed
-
Add mode where contrib installcheck runs each module in a separately named database.
- ad69bd052f8a 9.3.0 cited