From: | Jeff Frost <jeff(at)pgexperts(dot)com> |
---|---|
To: | Laurent Wandrebeck <l(dot)wandrebeck(at)quelquesmots(dot)fr> |
Cc: | pgsql-pkg-yum(at)postgresql(dot)org |
Subject: | Re: RHEL7 pgbouncer package /run/pgbouncer rights glitch after reboot |
Date: | 2015-06-03 14:56:04 |
Message-ID: | 5B39E46F-635D-46D1-ACC0-CC4D4D256917@pgexperts.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-yum |
> On Jun 2, 2015, at 10:33 PM, Laurent Wandrebeck <l(dot)wandrebeck(at)quelquesmots(dot)fr> wrote:
>
>
> 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 :)
It’s not necessarily nonsense, but it’s likely to break quite a few existing apps that expect it in /tmp. If we decided to go this way, we would probably only do it on new distros.
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GÜNDÜZ | 2015-06-05 05:41:03 | Fedora 22 status |
Previous Message | Laurent Wandrebeck | 2015-06-03 05:33:31 | Re: RHEL7 pgbouncer package /run/pgbouncer rights glitch after reboot |