Storing config in the data directory - Mailing list pgsql-pkg-debian

From Vincent Jaubert
Subject Storing config in the data directory
Date
Msg-id joTSP8Gf_Ec9u_ZOxo4Q5ma-rhbpggT0MEr5zSl3X9wL8_BCd2muDNy9WPLZCYADrTl3s5ZGI5G_KNnL4nVW1tJ8O1C-eQIMq8Mp8o9nNj4=@vjaubert.com
Whole thread Raw
List pgsql-pkg-debian
Hi everyone,
i am somewhat struggling with the postgres 16.4 package on Ubuntu. I hope this is the correct mailing list to ask this question.
I am using postgresql on servers deployed in the cloud.
I would like to host both postgres data and config in an attached network storage (block storage). This way, when i want to recreate a new server, i have just to use the same block storage as the previous server to continue working with minimal interruption.
So at boot time, the block storage is mounted at /var/lib/postgresql
The problem is that the debian package choose to store config in /etc/postgresql instead.
I tried various workarounds :
  • create a bind mount in /etc/postgresql and another in /var/lib/postgresql
  • store settings in /var/lib/postgresql and create a symlink in /etc/postgresql
Both ways work, but when doing like this, for some reason the server is not restarting at bootup.
When running manually `systemctl start postgresql` it works,  but whatever i tried, i can't get it to start at boot. I have read dozens of logs, and i don't see any error anywhere.
I am also concerned that in case of failure, the server would not restart.
What could be the source of this ?

Thank you.

Vincent Jaubert

pgsql-pkg-debian by date:

Previous
From: Moritz Mühlenhoff
Date:
Subject: Re: PostgreSQL CVE-2024-7348 today
Next
From: apt.postgresql.org Repository Update
Date:
Subject: elephant-shed updated to version 1.3.9.pgdg+1