Re: RHEL7 pgbouncer package /run/pgbouncer rights glitch after reboot

From: Laurent Wandrebeck <l(dot)wandrebeck(at)quelquesmots(dot)fr>
To: Jeff Frost <jeff(at)pgexperts(dot)com>
Cc: pgsql-pkg-yum(at)postgresql(dot)org
Subject: Re: RHEL7 pgbouncer package /run/pgbouncer rights glitch after reboot
Date: 2015-06-03 05:33:31
Message-ID: 24ca4e97-ed15-43ab-b5a7-b60d25a7b9b8@email.android.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-pkg-yum


Le 2 juin 2015 22:28, Jeff Frost <jeff(at)pgexperts(dot)com> a écrit :
>
>
> Oh, so you’re suggesting that pgbouncer use both socket directories as well?
>
> That would require a pgbouncer patch to support multiple socket locations.
>

Actually, I'm not :) I just copied changelog linked to that /var/run stuff, sorry it puzzled you.

Just suggested:
- Postgres user for both.
- /var/run/postgresql for sockets.

Do you think it could bring problems ? (ie apps using hardcoded path to find pg socket ?)
According to pgbouncer config file, it looks like debian uses /var/run/postgresql for a while, so I hope my proposal doesn't land in nonsense territory :)

Laurent

In response to

Responses

Browse pgsql-pkg-yum by date

  From Date Subject
Next Message Jeff Frost 2015-06-03 14:56:04 Re: RHEL7 pgbouncer package /run/pgbouncer rights glitch after reboot
Previous Message Jeff Frost 2015-06-02 20:28:54 Re: RHEL7 pgbouncer package /run/pgbouncer rights glitch after reboot