Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit ca1d4eb

Browse files
committed
Remove forced CHECKPOINT in regression tests --- redundant now that
CREATE DATABASE does one internally.
1 parent fbcbc5d commit ca1d4eb

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

src/test/regress/pg_regress.sh

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
#! /bin/sh
2-
# $PostgreSQL: pgsql/src/test/regress/pg_regress.sh,v 1.57 2005/06/21 04:02:34 tgl Exp $
2+
# $PostgreSQL: pgsql/src/test/regress/pg_regress.sh,v 1.58 2005/06/25 23:04:06 tgl Exp $
33

44
me=`basename $0`
55
: ${TMPDIR=/tmp}
@@ -535,9 +535,6 @@ fi
535535
# Create the regression database
536536
# We use template0 so that any installation-local cruft in template1
537537
# will not mess up the tests.
538-
# Note: the reason for checkpointing just after creating the new DB is so
539-
# that if we get a backend core dump during the tests, WAL replay won't
540-
# remove the core file.
541538
# ----------
542539

543540
message "creating database \"$dbname\""
@@ -548,7 +545,6 @@ if [ $? -ne 0 ]; then
548545
fi
549546

550547
"$bindir/psql" -q -X $psql_options -c "\
551-
checkpoint;
552548
alter database \"$dbname\" set lc_messages to 'C';
553549
alter database \"$dbname\" set lc_monetary to 'C';
554550
alter database \"$dbname\" set lc_numeric to 'C';

0 commit comments

Comments
 (0)