Re: pgbouncer packaging issue
От
Peter Eisentraut
Тема
Re: pgbouncer packaging issue
Дата
Msg-id
fd1a79a4-2c65-aa25-d1e7-0a184e0a16a6@2ndquadrant.com
Ответ на
Re: pgbouncer packaging issue (Christoph Berg)
Список
Дерево обсуждения
pgbouncer packaging issue Brandon Snider <brandonjsnider@gmail.com>
Re: pgbouncer packaging issue Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: pgbouncer packaging issue Christoph Berg <cb@df7cb.de>
Re: pgbouncer packaging issue Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: pgbouncer packaging issue Devrim Gündüz <devrim@gunduz.org>
On 1/9/18 16:11, Christoph Berg wrote: > Am 9. Januar 2018 19:59:04 MEZ schrieb Peter Eisentraut : >> 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
В списке pgsql-pkg-yum по дате отправления