From 5a5edc26e4a18a63d28cad3448d003dd0e939232 Mon Sep 17 00:00:00 2001
From: Arnaud Poncet-Montanges <ponceta@users.noreply.github.com>
Date: Thu, 14 Sep 2017 14:02:42 +0200
Subject: [PATCH] Add debuging hints (#193)

Add debuging hints to ease the update process.
---
 update/upgrade_db.README | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/update/upgrade_db.README b/update/upgrade_db.README
index 07ff1f95..01bb1cc1 100644
--- a/update/upgrade_db.README
+++ b/update/upgrade_db.README
@@ -31,3 +31,13 @@ The process will create a qwat_test and a qwat_test_conform DB.
 
 If the process is successfull, you will be able to migrate your real database by lauching the command again with " --upgrade yes " parameter. Otherwise, the process is only launched on test DB.
 
+**************
+Debuging Hints
+**************
+On https://github.com/qwat/qwat-data-model/blob/master/update/upgrade_db.sh#L136
+
+   --single-transaction --exit-on-error 
+
+Can be problematic on restore : see https://lists.osgeo.org/pipermail/postgis-users/2015-November/040950.html
+
+Avoiding quiet mode -q can be a great help to determine which query is failing.