[Pkg-postgresql-public] Bug#755894: confirmed on an ARM server for postgreSQL 9.4

Luc Maisonobe luc at spaceroots.org
Sat Aug 9 15:28:32 UTC 2014

I encountered the same behaviour on a small ARM server running Jessie
(PostgreSQL-9.4, version 159).

I noticed it after investigating why bacula-director did not start
anymore. It was in fact due to postgreSQL not having started beforehand.

Starting postgreSQL manually by running "systemctl start postgresql"
does work. The postgresql.service appears as "active (exited)" after the
start, and the postgresql at 9.4-main.service appears as "active (running)"
at the same time. Everything runs fine afterwards.

best regards,

More information about the Pkg-postgresql-public mailing list