Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d3ghT-0007t2-RV for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 27 Apr 2017 10:31:03 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d3ghT-0003XB-E7 for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 27 Apr 2017 10:31:03 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d3ghP-0003QR-AJ for pgsql-pkg-yum@postgresql.org; Thu, 27 Apr 2017 10:30:59 +0000 Received: from ns5.gunduz.org ([107.170.136.15] helo=ns1.gunduz.org) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d3ghM-0004w0-F4 for pgsql-pkg-yum@postgresql.org; Thu, 27 Apr 2017 10:30:58 +0000 Received: from asus-laptop03.gunduz.org (unknown [46.154.59.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ns1.gunduz.org (Postfix) with ESMTPSA id 5DF0E3FD09; Thu, 27 Apr 2017 10:30:54 +0000 (UTC) Message-ID: <1493289043.3032.43.camel@gunduz.org> Subject: Re: pgbouncer socket directory From: Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= To: Peter Eisentraut , pgsql-pkg-yum@postgresql.org Date: Thu, 27 Apr 2017 13:30:43 +0300 In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-ZrtKlfSNiNZ9khQgWs//" X-Mailer: Evolution 3.22.6 (3.22.6-2.fc25) Mime-Version: 1.0 X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-pkg-yum Precedence: bulk Sender: pgsql-pkg-yum-owner@postgresql.org --=-ZrtKlfSNiNZ9khQgWs// Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Peter, On Wed, 2017-04-26 at 08:47 -0400, Peter Eisentraut wrote: > The postgresql packages are configured with a socket directory > /var/run/postgresql, but pgbouncer is configured with /tmp.=C2=A0 Hmm, I think I forgot to patch that part -- we create /var/run/pgbouncer, a= nd expect socket file there. > Those should probably be the same, so that clients can connect to either > one. I pass -h /tmp to psql to make this work. I see your point, though. > But /var/run/postgresql is 0755 postgres:postgres, so pgbouncer can't > write there.=C2=A0=C2=A0How is this supposed to work? No idea. Anyone else? Regards, --=20 Devrim G=C3=BCnd=C3=BCz EnterpriseDB: http://www.enterprisedb.com PostgreSQL Dan=C4=B1=C5=9Fman=C4=B1/Consultant, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR --=-ZrtKlfSNiNZ9khQgWs// Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJZAchTAAoJENjDPf6Sz261Qy0QAIbmkp+ax9KuDNH8CrRKV51E 0jSZ2smzwXH0OrZRePT5P5fOnlxtenNIen9lBkUuwmjgCw2bV4Z3bD0ki7KXqQ1b MDzZPYjJHIvuZ4jJTkbl3OFHP35+/LpCJqpfye5ZQPMc8xG+O4coRMv0DBjAZOU0 901uuNw1cP6nS3uATYsfvpo3sNx1HqUfBBX2atnMKb9tRqCdYNfKfeDNOCbeaRK8 sd57aqjhOVUy0TNio4Bd8dfaUbQ95drXgFWELiA1OcrJXuIKbLVccEn7NTuLc/Mi Ha7ycM/DQjP+eANrIJXap1UmQO/Gieh5hyZoaZQhSKQVLAHJ73p8jFM6zzu7IQHr KDE6d2EZTefhPQ3+4vOzwDsA9hozWUXO2abLzMSpf/+kBKf2XAZ+I6zC5OWc63FL dO63NNv9Ys9B4+UFCcvMoC87iMjftXv3gH3AJEOMn0dHX8UBWTp4rwdNE8tVCVRq zCshZnOqfPU39EkskJpcdJiyUuA92ULVRPPZEgQB92nD7S141kzACG6UWQIySknb AsYoy4bt7XhM8IBta9ltAprBu+PR4sSKzAAePpmS6x5E/UoXnA4Fc4oPAWOMX5Ze NaAU0LMZRARYmFzXNm6D9VaT4ERvCGsTwJyzZdrmXAXrCXKpe5b3qFV6DrvPBMCo rLRNrNA6xB90BzZAOHTc =KWMA -----END PGP SIGNATURE----- --=-ZrtKlfSNiNZ9khQgWs//--