A service which depends on postgresql (using the recommended Requires=/After= pair) is also affected by this, because the service cannot immediately connect to Postgres at startup.
This patch seems to make start/stop work for me, although it doesn't do anything about reload: --- a/postgresql@.service 2014-08-11 14:40:56.000000000 +0100 +++ b/postgresql@.service 2014-09-09 15:44:32.489366245 +0100 @@ -8,10 +8,12 @@ ConditionPathExists=/etc/postgresql/%I/postgresql.conf PartOf=postgresql.service ReloadPropagatedFrom=postgresql.service +Before=postgresql.service [Service] # @: use "postgresql@%i" as process name -ExecStart=@/usr/bin/pg_ctlcluster postgresql@%i --foreground --stdlog %i start +Type=forking +ExecStart=@/usr/bin/pg_ctlcluster postgresql@%i --stdlog %i start ExecStop=/usr/bin/pg_ctlcluster -m fast %i stop ExecReload=/usr/bin/pg_ctlcluster %i reload PIDFile=/var/run/postgresql/%i.pid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
