[Pkg-postgresql-public] Systemd starts postgresql before network

Phil Endecott spam_from_debian_postgresql at chezphil.org
Thu Feb 1 17:32:18 UTC 2018

Dear Experts,

I have been experimenting with streaming replication to a hot
standby server on AWS.  Everything works remarkably well, except
that the replica cluster doesn't start after a reboot.

The underlying issue seems to be that systemd tries to starts the
cluster very early in the boot process, before the network is up.
It fails to start because it needs the network for the replication
connection and/or the data is actually on an AWS NFS-like
networked filesystem.

I think there is a corresponding issue at shutdown, i.e. the
network goes down and the filesystem disappears from underneath
the still-running postgresql process.  This causes a long timeout.

Is this a bug?  Should the postgresql systemd config require
that the network is up before it starts?  If not, what's the
"right way" for me to fix this locally?

Thanks for any suggestions.

Regards, Phil.

More information about the Pkg-postgresql-public mailing list