On Tue, Mar 11, 2025 at 08:25:15PM +0100, Michael Banck wrote:
> > But I'm not sure if it's an upstream bug, or a latent flaw in the Debian
> > packaging.
>
> I had another look today and I think it is an upstream thing
To clarify this a bit: Patroni renames the original postgresql.conf
(that has
Hi,
On Wed, Jan 31, 2024 at 05:28:34PM +, Ben Harris wrote:
> 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 n
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-
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.
4 matches
Mail list logo
