summaryrefslogtreecommitdiff
path: root/contrib/pg_upgrade/TESTING
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2011-11-27 22:42:32 +0200
committerPeter Eisentraut <peter_e@gmx.net>2011-11-27 22:42:32 +0200
commit08da2d282f1c3cbff141ecd218d737990cf6d234 (patch)
tree28bab8e043eacd472d8129f5aa11ef84af99c21e /contrib/pg_upgrade/TESTING
parent8722a1a06aedbbbeb4f848a7b9ee62d6ae8649c6 (diff)
downloadpostgresql-08da2d282f1c3cbff141ecd218d737990cf6d234.tar.gz
Add pg_upgrade test suite
It runs the regression tests, runs pg_upgrade on the populated database, and compares the before and after dumps. While not actually a cross-version upgrade, this does detect omissions and bugs in the involved tools from time to time. It's also possible to do a cross-version upgrade by manually supplying parameters.
Diffstat (limited to 'contrib/pg_upgrade/TESTING')
-rw-r--r--contrib/pg_upgrade/TESTING19
1 files changed, 19 insertions, 0 deletions
diff --git a/contrib/pg_upgrade/TESTING b/contrib/pg_upgrade/TESTING
index f685c938c5..d38b205f49 100644
--- a/contrib/pg_upgrade/TESTING
+++ b/contrib/pg_upgrade/TESTING
@@ -62,3 +62,22 @@ steps:
7) Diff the regression database dump file with the regression dump
file loaded into the old server.
+
+The shell script test.sh in this directory performs more or less this
+procedure. You can invoke it by running
+
+ gmake check
+
+or by running
+
+ gmake installcheck
+
+if "gmake install" (or "gmake install-world") were done beforehand.
+When invoked without arguments, it will run an upgrade from the
+version in this source tree to a new instance of the same version. To
+test an upgrade from a different version, invoke it like this:
+
+ gmake installcheck oldbindir=...otherversion/bin oldsrc=...somewhere/postgresql
+
+In this case, you will have to manually eyeball the resulting dump
+diff for version-specific differences, as explained above.