Remove forced CHECKPOINT in regression tests --- redundant now that

CREATE DATABASE does one internally.

diff --git a/src/test/regress/pg_regress.sh b/src/test/regress/pg_regress.sh
index c192edc51569d85a55336de4000f399c6e48bc91..0ebb6621657d57520b774b3fac2ca106a5e34d8e 100644 (file)
--- a/src/test/regress/pg_regress.sh
+++ b/src/test/regress/pg_regress.sh
@@ -1,5 +1,5 @@
 #! /bin/sh
-# $PostgreSQL: pgsql/src/test/regress/pg_regress.sh,v 1.57 2005/06/21 04:02:34 tgl Exp $
+# $PostgreSQL: pgsql/src/test/regress/pg_regress.sh,v 1.58 2005/06/25 23:04:06 tgl Exp $
 
 me=`basename $0`
 : ${TMPDIR=/tmp}
@@ -535,9 +535,6 @@ fi
 # Create the regression database
 # We use template0 so that any installation-local cruft in template1
 # will not mess up the tests.
-# Note: the reason for checkpointing just after creating the new DB is so
-# that if we get a backend core dump during the tests, WAL replay won't
-# remove the core file.
 # ----------
 
 message "creating database \"$dbname\""
@@ -548,7 +545,6 @@ if [ $? -ne 0 ]; then
 fi
 
 "$bindir/psql" -q -X $psql_options -c "\
-checkpoint;
 alter database \"$dbname\" set lc_messages to 'C';
 alter database \"$dbname\" set lc_monetary to 'C';
 alter database \"$dbname\" set lc_numeric to 'C';