Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rT7Io-000YSb-Rz for pgsql-general@arkaria.postgresql.org; Thu, 25 Jan 2024 21:30:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rT7In-004U50-W7 for pgsql-general@arkaria.postgresql.org; Thu, 25 Jan 2024 21:30:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rT7In-004U3z-Ls for pgsql-general@lists.postgresql.org; Thu, 25 Jan 2024 21:30:25 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rT7Il-003iHu-Dj for pgsql-general@lists.postgresql.org; Thu, 25 Jan 2024 21:30:25 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 40PLUKLH455827; Thu, 25 Jan 2024 16:30:20 -0500 From: Tom Lane To: Ron Johnson cc: Adrian Klaver , Atul Kumar , pgsql-general Subject: Re: permission denied on socket In-reply-to: References: Comments: In-reply-to Ron Johnson message dated "Thu, 25 Jan 2024 15:39:50 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <455825.1706218220.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Thu, 25 Jan 2024 16:30:20 -0500 Message-ID: <455826.1706218220@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Ron Johnson writes: > On Thu, Jan 25, 2024 at 3:32 PM Adrian Klaver > wrote: >> Best guess is you are using a version of psql that is expecting the >> socket to be somewhere else then where it actually is. > Is "permission denied" really the error you get when the socket does not > exist? Nope, that should mean either that /tmp is not readable, or that the socket file is there but has restrictive permissions. That doesn't necessarily make Adrian's answer wrong though. regards, tom lane