postgrespro
diff --git a/‎src/pgpro-upgrade/pgpro_version.sql renamed to ‎src/pgpro-upgrade/001-pgpro_version.sql b/‎src/pgpro-upgrade/pgpro_version.sql renamed to ‎src/pgpro-upgrade/001-pgpro_version.sql
diff --git a/‎src/pgpro-upgrade/pgpro_version.test renamed to ‎src/pgpro-upgrade/001-pgpro_version.test b/‎src/pgpro-upgrade/pgpro_version.test renamed to ‎src/pgpro-upgrade/001-pgpro_version.test
diff --git a/‎src/pgpro-upgrade/covering_index.sql renamed to ‎src/pgpro-upgrade/002-covering_index.sql b/‎src/pgpro-upgrade/covering_index.sql renamed to ‎src/pgpro-upgrade/002-covering_index.sql
diff --git a/‎src/pgpro-upgrade/covering_index.test renamed to ‎src/pgpro-upgrade/002-covering_index.test b/‎src/pgpro-upgrade/covering_index.test renamed to ‎src/pgpro-upgrade/002-covering_index.test
diff --git a/‎src/pgpro-upgrade/covering_index_2.sql renamed to ‎src/pgpro-upgrade/003-covering_index_2.sql b/‎src/pgpro-upgrade/covering_index_2.sql renamed to ‎src/pgpro-upgrade/003-covering_index_2.sql
diff --git a/‎src/pgpro-upgrade/covering_index_2.test renamed to ‎src/pgpro-upgrade/003-covering_index_2.test b/‎src/pgpro-upgrade/covering_index_2.test renamed to ‎src/pgpro-upgrade/003-covering_index_2.test
diff --git a/‎src/pgpro-upgrade/README
Lines changed: 17 additions & 0 deletions b/‎src/pgpro-upgrade/README
Lines changed: 17 additions & 0 deletions
diff --git a/‎src/pgpro-upgrade/pgpro_upgrade
Lines changed: 26 additions & 8 deletions b/‎src/pgpro-upgrade/pgpro_upgrade
Lines changed: 26 additions & 8 deletions
@@ -27,6 +27,10 @@ because it starts postgres in single-user mode to perform upgrades.
 It is safe to invoke script multiple times, because it does check for
 features it is going to add.
 
+If script is invoked with **--check** argument, it doesn't do any
+changes in the database, just returns 0 if no changes is needed, 
+and 1 if base needs to be upgraded.
+
 HOW TO ADD NEW FEATURE
 ----------------------
 
@@ -44,3 +48,16 @@ which returns single boolean value (i.e. one column and one row). This
 value should be 'f' if feature is not found in the database and should
 be installed, and 't' if it already exists.
 
+Note that scirpts are invoked using postgres single-user mode, not using
+psql. So, each SQL statement should be in one line or line endings
+should be \ esaped.
+
+Last line of the script should contain newline at the end.
+
+Script naming convention
+------------------------
+
+Scripts are executed in the lexicographical order of their names.
+So, please start name of script with 3-digit number, next one to last
+used, followed by dash.
+
@@ -4,10 +4,14 @@
 # 3. sed 
 if [ -z "$PGDATA" ]; then
 	echo "PGDATA environment variable is not set. Stop." 1>&2
-	exit 1
+	exit 2
 fi
 PGBIN="`echo $0|sed 's![^/\\]*$!!'`"
-
+if [ "$1" = "--check" ]; then
+   check=1
+else
+   check=
+fi
 echo "$PGBIN"
 
 case "$PGBIN" in
@@ -38,17 +42,31 @@ if [ -z "$BASELIST" ]; then
 	exit 1
 fi
 
-echo "Upgrading databases $BASELIST"
+[ -z "$check" ]&& echo "Upgrading databases $BASELIST"
 
 #Search for upgrade scripts
+need_upgrade=0
 for i in "$DIR"/*.test; do
-	create="`echo "$i" |sed 's/\.test$/.sql/'`"
 	found=`< "$i"  "${PGBIN}postgres" --single template0 | 
 		sed -n 's/^[	 ]*1: [^ ]* = "\([ft]\)"[ 	].*$/\1/p'` 
 	if [ "$found" = "f" ]; then	
-		for base in $BASELIST; do
-			echo "Executing $create in $base"
-			< "$create"  "${PGBIN}postgres" --single "$base"
-		done
+		if [ -z "$check" ]; then
+			create="`echo "$i" |sed 's/\.test$/.sql/'`"
+			for base in $BASELIST; do
+				echo "Executing $create in $base"
+				< "$create"  "${PGBIN}postgres" --single "$base" >/dev/null
+
+			done
+		else 
+			need_upgrade=1
+		fi
 	fi
 done
+if [ -n "$check" ]; then
+	if [ $need_upgrade -eq 0 ]; then
+		echo "All Postgres Pro specific updates are appied" 1>&2
+	else
+		echo "Database needs upgrade"
+	fi
+	exit $need_upgrade
+fi