@@ -47,10 +47,10 @@ pg_isolation_regress is a tool similar to pg_regress, but instead of using
47
47
psql to execute a test, it uses isolationtester. It accepts all the same
48
48
command-line arguments as pg_regress.
49
49
50
- By default, isolationtester will wait at most 300 seconds (5 minutes)
50
+ By default, isolationtester will wait at most 360 seconds (6 minutes)
51
51
for any one test step to complete. If you need to adjust this, set
52
- the environment variable PGISOLATIONTIMEOUT to the desired timeout
53
- in seconds.
52
+ the environment variable PG_TEST_TIMEOUT_DEFAULT to half the desired
53
+ timeout in seconds.
54
54
55
55
56
56
Test specification
@@ -138,10 +138,11 @@ Each step may contain commands that block until further action has been taken
138
138
deadlock). A test that uses this ability must manually specify valid
139
139
permutations, i.e. those that would not expect a blocked session to execute a
140
140
command. If a test fails to follow that rule, isolationtester will cancel it
141
- after PGISOLATIONTIMEOUT seconds. If the cancel doesn't work, isolationtester
142
- will exit uncleanly after a total of twice PGISOLATIONTIMEOUT. Testing
143
- invalid permutations should be avoided because they can make the isolation
144
- tests take a very long time to run, and they serve no useful testing purpose.
141
+ after 2 * PG_TEST_TIMEOUT_DEFAULT seconds. If the cancel doesn't work,
142
+ isolationtester will exit uncleanly after a total of 4 *
143
+ PG_TEST_TIMEOUT_DEFAULT. Testing invalid permutations should be avoided
144
+ because they can make the isolation tests take a very long time to run, and
145
+ they serve no useful testing purpose.
145
146
146
147
Note that isolationtester recognizes that a command has blocked by looking
147
148
to see if it is shown as waiting in the pg_locks view; therefore, only
0 commit comments