Subject: Re: pgbouncer packaging issue
To: Christoph Berg <cb@df7cb.de>, pgsql-pkg-yum@lists.postgresql.org,
 Brandon Snider <brandonjsnider@gmail.com>, pgsql-pkg-yum@postgresql.org
References: 
 <CABSshC2iCU9+DeT8vvBXvYzJmMmjYM3CVshccRwDv7Pf-vMYrw@mail.gmail.com>
 <cb4e58aa-6351-c6e5-18c7-c5e8de0e788f@2ndquadrant.com>
 <1B26AE81-A323-48BF-BA9D-25E936A35A9E@df7cb.de>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <fd1a79a4-2c65-aa25-d1e7-0a184e0a16a6@2ndquadrant.com>
Date: Wed, 10 Jan 2018 09:56:59 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <1B26AE81-A323-48BF-BA9D-25E936A35A9E@df7cb.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 1/9/18 16:11, Christoph Berg wrote:
> Am 9. Januar 2018 19:59:04 MEZ schrieb Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
>> On 1/9/18 13:47, Brandon Snider wrote:
>>> You're installing /usr/lib/tmpfiles.d/pgbouncer.conf to create the
>>> /var/run/pgbouncer dir, but the permissions on that dir are too
>>> restrictive -- 700 -- for any file to be read by any user except
>>> pgbouncer and root. In my situation, for whatever reason my PHP
>>> implementation can't read unix sockets in /tmp,
>>
>> That might need further explanation.
> 
> That's likely systemd at work. By default, each process gets its own /tmp bind-mounted.

Right.  After further off-list discussion, the actual bug here is that
pgbouncer should puts its socket into /var/run/postgresql, which is the
standard location on that platform.  But that doesn't work because
pgbouncer runs under a separate user and doesn't have permission there.
This has been previously reported on this list.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services