public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Brandon Snider <[email protected]>
To: [email protected]
Subject: Re: pgbouncer packaging issue
Date: Tue, 9 Jan 2018 13:59:04 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABSshC2iCU9+DeT8vvBXvYzJmMmjYM3CVshccRwDv7Pf-vMYrw@mail.gmail.com>
References: <CABSshC2iCU9+DeT8vvBXvYzJmMmjYM3CVshccRwDv7Pf-vMYrw@mail.gmail.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.

> and I would like to
> install the socket to the /var/run dir since the pgbouncer user has
> write permissions there. This is a very similar situation as the
> postgresql conf file which creates the /var/run/postgresql dir. I
> could manually change the directory permission myself, but it would be
> overwritten the next time there's a bouncer update.

Depending on the operating system, you should put the socket into /tmp
or /var/run/postgresql, because that's where a PostgreSQL client would
expect it.  The client isn't supposed to know that it's connecting to
pgbouncer instead.  So /var/run/pgbouncer is in any case not a
designated place for a Unix-domain socket.

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

view thread (5+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: pgbouncer packaging issue
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox