[Bug 1749283] Re: configured stats_temp_directory does not get created after reboot
tsimonq2 at ubuntu.com
Fri Aug 17 05:16:01 UTC 2018
Unsubscribing sponsors for now; Brian is right.
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
configured stats_temp_directory does not get created after reboot
Status in postgresql-common package in Ubuntu:
Status in resource-agents package in Ubuntu:
Status in postgresql-common source package in Xenial:
Status in resource-agents source package in Xenial:
Status in postgresql-common source package in Artful:
Status in resource-agents source package in Artful:
Status in postgresql-common source package in Bionic:
Status in resource-agents source package in Bionic:
Status in postgresql-common package in Debian:
Default postgres installation in Ubuntu (and Debian) configures
stats_temp_directory inside /var/run/postgresql:
$ grep stats_temp /etc/postgresql/10/main/postgresql.conf
stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp'
However, this directory is not created after reboot.
In most cases this is not a problem as systemd starts postgres via
pg_ctlcluster, a "multiversion/cluster aware pg_ctl wrapper", and
pg_ctlcluster will create missing directories before starting
But in cases where systemd is not starting postgres this is a problem.
Specifically, when postgres is controlled by pacemaker (using postgres resource agent for pacemaker) it is started using pg_ctl wrapper. pg_ctl won't create missing directories and therefore postgres fails to start.
The simplest solution for this issue is to have systemd recreate
missing directories via /usr/lib/tmpfiles.d/postgresql.conf file.
Currently only /var/run/postgresql and /var/log/postgresql are created
To manage notifications about this bug go to:
More information about the Ubuntu-sponsors