fix: put postgres back on the NAS and revert the c72389c refactor #20
Loading…
Reference in a new issue
No description provided.
Delete branch "hotfix/postgres-datadir"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The cum-services deploy failed because postgres was running the wrong
cluster.
42c2ee0(wysi) removeddataDir = "/mnt/main-hdd/pg", so themodule fell back to
/var/lib/postgresql/18: a stale local cluster withnone of the app roles or databases.
postgresql-setupthen tried to createall of them from a
template1that predates the glibc 2.42 bump and failedon the collation version mismatch. The real data on the NAS was never
touched.
The
c72389crefactor made the same mistake on cum-media, dropping itsservices.postgresql.dataDir, so that host would break the same way on itsnext deploy.
What
dataDir = "/mnt/main-hdd/pg".c72389cand its fixup42f3919. This brings backcum-media's
dataDir, the per-host NAS mounts, NetworkManager, the old usergroups and docker socket symlinks, and the flake-parts devShell/formatter.
It also removes
nixos/nfs.nix, which only that refactor used.All five hosts evaluate.
After deploying
under glibc 2.40). They don't block anything now that no new database has to
be created. Reindex and run
REFRESH COLLATION VERSIONon each database whenconvenient.
/var/lib/postgresql/18on cum-services is the stale cluster. Delete it oncethe services are confirmed healthy on the NAS one.
Generated with Claude Code
c72389csystem refactor 4c28f9b589