for standalone backends.
Although we probably ought to just remove this long-obsolete test case from
our code, it seems worthwhile to document the issue and fix in CVS first.
Jeff Janes
fi
echo =============== destroying old bench database... =================
-echo "drop database bench" | postgres -D"$1" postgres > /dev/null
+echo "drop database bench" | postgres --single -D"$1" postgres > /dev/null
echo =============== creating new bench database... =================
-echo "create database bench" | postgres -D"$1" postgres > /dev/null
+echo "create database bench" | postgres --single -D"$1" postgres > /dev/null
if [ $? -ne 0 ]; then
echo createdb failed
exit 1
fi
-postgres -D${1} bench < create.sql > /dev/null
+postgres --single -D${1} bench < create.sql > /dev/null
if [ $? -ne 0 ]; then
echo initial database load failed
exit 1
fi
echo =============== vacuuming benchmark database... ================= >&2
-echo "vacuum" | postgres -D"$1" bench > /dev/null
+echo "vacuum" | postgres --single -D"$1" bench > /dev/null
echo =============== running benchmark... ================= >&2
-time postgres -D"$1" -texecutor -tplanner -c log_min_messages=log -c log_destination=stderr -c start_log_collector=off bench < bench.sql 2>&1
+time postgres --single -D"$1" -texecutor -tplanner -c log_min_messages=log -c log_destination=stderr -c logging_collector=off bench < bench.sql 2>&1