From ec52e0e38f859eb7edbde62108f0a596699d196a Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 24 Aug 2009 03:10:16 +0000 Subject: [PATCH] Run the "tablespace" regression test first not last. The former placement renders useless one of the few test methodologies we have for WAL replay, which is to intentionally crash the system just after completing the regression tests and see if it recovers to the expected database state. The reason is that DROP TABLESPACE forces a checkpoint, so there's essentially no WAL available for replay after the tests complete. --- src/test/regress/parallel_schedule | 8 +++++--- src/test/regress/serial_schedule | 2 +- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/src/test/regress/parallel_schedule b/src/test/regress/parallel_schedule index 9e0a6046cf..3605898d57 100644 --- a/src/test/regress/parallel_schedule +++ b/src/test/regress/parallel_schedule @@ -5,6 +5,11 @@ # this limits the number of connections needed to run the tests. # ---------- +# run tablespace by itself, and first, because it forces a checkpoint; +# we'd prefer not to have checkpoints later in the tests because that +# interferes with crash-recovery testing. +test: tablespace + # ---------- # The first group of parallel tests # ---------- @@ -89,6 +94,3 @@ test: plancache limit plpgsql copy2 temp domain rangefuncs prepare without_oid c # run stats by itself because its delay may be insufficient under heavy load test: stats - -# run tablespace by itself -test: tablespace diff --git a/src/test/regress/serial_schedule b/src/test/regress/serial_schedule index c13eb79a81..dc97b546b9 100644 --- a/src/test/regress/serial_schedule +++ b/src/test/regress/serial_schedule @@ -1,5 +1,6 @@ # $PostgreSQL$ # This should probably be in an order similar to parallel_schedule. +test: tablespace test: boolean test: char test: name @@ -121,4 +122,3 @@ test: largeobject test: with test: xml test: stats -test: tablespace -- 2.39.5