Bug#1062204: Newly-created clusters have restrictive postgresql.conf permissions

2025-02-12 Thread Ben Harris
Control: found -1 patroni/4.0.4-6 It's been a while since I reported this, so I thought I should check if Patroni was still leaving postgresql.conf with unhelpful permissions. I'm sorry to report that following my instructions on an up-to-date sid system still leads to unhappiness: -rw-

Bug#1062204: Newly-created clusters have restrictive postgresql.conf permissions

2024-01-31 Thread Ben Harris
Package: patroni Version: 3.2.2-1 When Patroni creates a new PostgreSQL cluster, the postgresql.conf file in /etc/patroni// ends up without world read permission. This means that tools that use pg_wrapper (such as /usr/bin/psql) can't find the cluster's port number and don't work by default.