service: avoid cryptic failure with old config

If user removes currently provided /etc/postgresql/postgresql
configuration file, PGDATA env variable is not set.  The
`systemctl start postgresql` would fail similarly to
`systemctl start postgresql@NOTCONFIGURED` when the configuration
file was not created yet with cryptic message
    "Usage: ... "

Stop this behavior rather explicitly with proper error in
check-db-dir script.

Warn also user in similar fashion that the configuration should be
adjusted in case the PGDATA was set directly in service file.

1 files changed, 8 insertions, 0 deletions

diff --git a/NEWS b/NEWS
index 9a17dac..52e7b82 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,13 @@
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+New in 0.9.2 version
+
+* The postgresql-check-db-dir is now more strict to admin's configuration
+  and tries to avoid future incompatibilities by warning about the
+  /etc/postgresql/$servicename file non-existence.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
 New in 0.9.1 version
 
 * The postgresql-setup script does not require --port option when upgrading.