rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Issue a CHECKPOINT just after creating the regression database. Without 

this, it's hard to debug core-dump test failures, because WAL replay will
enthusiastically remove the core file (along with the rest of the
regression database directory).  Per recent discussion, not to mention
bitter experience.
This commit is contained in:
Tom Lane 2004-09-22 19:11:19 +00:00
parent bebaf70613
commit 5d9f5c20dd
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/test/regress/pg_regress.sh
View File

@ -1,5 +1,5 @@
#! /bin/sh
# $PostgreSQL: pgsql/src/test/regress/pg_regress.sh,v 1.46 2004/08/10 22:24:06 tgl Exp $
# $PostgreSQL: pgsql/src/test/regress/pg_regress.sh,v 1.47 2004/09/22 19:11:19 tgl Exp $
me=`basename $0`
: ${TMPDIR=/tmp}
@ -510,6 +510,9 @@ 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\""
@ -520,6 +523,7 @@ if [ $? -ne 0 ]; then
fi
"$bindir/psql" $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';