Hello,
Postgres is started via pg_ctl and NOT systemd.
Below are the log entries when version 9.6.2-1 is started.
2017-04-04 07:15:27 AESTLOG: database system was shut down at 2017-04-
03 13:08:27 AEST
2017-04-04 07:15:28 AESTLOG: MultiXact member wraparound protections
are now enabled
2017-04-04 07:15:28 AESTLOG: database system is ready to accept
connections
2017-04-04 07:15:28 AESTLOG: autovacuum launcher started
Upgraded to version 9.6.2-2 and these are the log entries on start-up:-
2017-04-05 08:03:29 AESTLOG: test message did not get through on
socket for statistics collector
2017-04-05 08:03:29 AESTLOG: disabling statistics collector for lack
of working socket
2017-04-05 08:03:29 AESTWARNING: autovacuum not started because of
misconfiguration
2017-04-05 08:03:29 AESTHINT: Enable the "track_counts" option.
2017-04-05 08:03:29 AESTLOG: database system was shut down at 2017-04-
04 13:05:46 AEST
2017-04-05 08:03:30 AESTLOG: MultiXact member wraparound protections
are now enabled
2017-04-05 08:03:30 AESTLOG: database system is ready to accept
connections
It is ignoring the PGDATA path and obtaining postgresql.conf from
/etc/postgresql/9.6/main.
Removed all the Postgres conf files from the /etc path and it is back
working as intended.
Is this just something the Debian package maintainers have done or do
we have to alter the start-up scripts to specify the config_file
setting?
The doco says "By default, all three configuration files are stored in
the database cluster's data directory." which IMHO means where PGDATA
is pointing.
Has anybody else struck this issue?
Cheers,
Rob