Skip to content

Commit 963bafd

Browse files
committed
Remove prepared transactions from main isolation test schedule.
There is no point in running this test when prepared transactions are disabled, which is the default. New make targets that include the test are provided. This will save some useless waste of cycles on buildfarm machines. Backpatch to 9.1 where these tests were introduced.
1 parent 200ff8b commit 963bafd

File tree

2 files changed

+7
-1
lines changed

2 files changed

+7
-1
lines changed

src/test/isolation/Makefile

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,13 @@ maintainer-clean: distclean
7575
installcheck: all
7676
./pg_isolation_regress --psqldir='$(PSQLDIR)' --inputdir=$(srcdir) --schedule=$(srcdir)/isolation_schedule
7777

78+
# Version of the install check test that includes the prepared_transactions test
79+
# It only makes sense to run this if set up to use prepared transactions,
80+
# via the postgresql.conf.
81+
installcheck-prepared-txns: all
82+
./pg_isolation_regress --psqldir='$(PSQLDIR)' --inputdir=$(srcdir) --schedule=$(srcdir)/isolation_schedule prepared-transactions
83+
84+
7885
# We can't support "make check" because isolationtester requires libpq, and
7986
# in fact (on typical platforms using shared libraries) requires libpq to
8087
# already be installed. You could run "make install" and then run a check

src/test/isolation/isolation_schedule

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,3 @@ test: ri-trigger
99
test: partial-index
1010
test: two-ids
1111
test: multiple-row-versions
12-
test: prepared-transactions

0 commit comments

Comments
 (0)