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 1rz03L-001T2T-8H for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 20:14:15 +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 1rz03J-00FIj7-He for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 20:14:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rz03J-00FIir-6k for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 20:14:13 +0000 Received: from mail-vk1-xa36.google.com ([2607:f8b0:4864:20::a36]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rz03G-0048jV-PN for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 20:14:11 +0000 Received: by mail-vk1-xa36.google.com with SMTP id 71dfb90a1353d-4dabbd69c71so1288868e0c.1 for ; Mon, 22 Apr 2024 13:14:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713816850; x=1714421650; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=m40qxPLJowAYDWkAOGO0Gat7F6MncAV/nx9Pd2j+zgo=; b=YaPazN15PuGOcQOTdOstf3JqrXGp2Z0bPPCYvEK6/EljFnTRx/DHC4bWEYEJByoBvy F2CbN4s5NPz/Q2NEuT8BYdgk5EE4NURwNrY1H3kvSAUy2WKA8KhxkoBxl0RBmw50xiWw BNQGgHUFd3SYPIS9oYQLcpBbkFGlnR4ebDLKVATIqdDJtyLyGuRaImw6fNxWdHAtmx1g khAZKrslOHl4HViS/nBOVdizmTwafjeC4LNJr2XENffmAP6V20revYFFG3Ep+KY77Puv VNBBYPp4PvxHWbiIA9HlT71KliOfm1VnnDqUPYmmhSBWipgfp7iFvpIbWWUlJ/HOunIC 75/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713816850; x=1714421650; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=m40qxPLJowAYDWkAOGO0Gat7F6MncAV/nx9Pd2j+zgo=; b=jdlfGSNCZRkS+qTV5CfDcQiZEvtTu1KBNbi+LpNDVI15zrVC0tQTufXoKbEvkajxub j7G7zeJd6mK662jdsKaML664RI/5ejo+HeTIj+6FDUAbUeJF+ptmHvHeXKg6brrOd+AV 43QZcNWgZktzJU7sqSQdA4oxRY+GxJclhsEhcTAUfW4fEKMV9woA5zADXbEoi8Vb04Fe n1uWs1NbDI/LylG8Yk2v3txqTMPbdonLahVSUSpbPudFNcO95cZdDXrLgZWLq+OypITx vYUA9g+bkAl1EjHt0c4z4vESe9Bn+E1CEOJVeQU6HKSsaBSc42hvgYsxJg73LkzMol+o A1vg== X-Gm-Message-State: AOJu0Yy913NW5CwuyQvVDuzkXA++C+4NciUIbu9moZog35Pqp5t4GS1F HFY+hHuuCnrWPv2ESJuZnhsiAzeyCHqIDaGyji1qiIL9GbzSI6AZQ3AIYF5ocoKiE/O/LfzyPCK oNf8Wbw0S2pxAdapnkqN06aZPvE0OZGiw X-Google-Smtp-Source: AGHT+IEE8jbD4vPiGkFkciPToOmrzXD4IOZYE2Ag0kGmc7KP4sYVmvmIolM+xAEIR/VD2zDopyGq7aer3k8ZjJp5wtc= X-Received: by 2002:a67:fe07:0:b0:47b:c92c:d841 with SMTP id l7-20020a67fe07000000b0047bc92cd841mr12305106vsr.17.1713816849563; Mon, 22 Apr 2024 13:14:09 -0700 (PDT) MIME-Version: 1.0 From: Atul Kumar Date: Tue, 23 Apr 2024 01:43:58 +0530 Message-ID: Subject: issue with reading hostname To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000874a250616b51439" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000874a250616b51439 Content-Type: text/plain; charset="UTF-8" Hi, I have postgresql version 15 running on centos7. I have below query that reads hostname from /tmp directory: psql postgres -A -t -p 5432 -h /tmp/ -c 'SELECT pg_is_in_recovery();' so below are my questions: 1. Is the psql client reading the socket file that resides in the /tmp directory to fetch the hostname ? 2. I saw the socket file in /tmp and it is empty. Then how is the psql client still reading the socket file successfully for hostname ? this is my socket looks ( the size is 0 as the file is empty): srwxrwxrwx. 1 postgres postgres 0 Apr 22 12:47 .s.PGSQL.5432 Please help me clarify these doubts. Regards. --000000000000874a250616b51439 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I have postgresql=C2=A0 version= 15 running on centos7.

I have below query that re= ads hostname from /tmp directory:

psql postgres -A -t -p 5432 -h /tmp/= -c 'SELECT pg_is_in_recovery();'


so below are my questions:

1. Is the ps= ql client reading the socket file that resides in the /tmp directory to fet= ch the hostname ?

2. I saw the socket file in /tmp and it is em= pty. Then how is the psql client still reading the socket file successfully= =C2=A0for hostname ?


this is my socket looks (= the size is 0 as the file is empty):

srwxrwxrwx.=C2=A0 1 postgres postgres=C2=A0 =C2=A0 =C2=A0 0 Apr 22 12:47 .s.PGSQL.5432


Please help me clarify these doubts.



Regards.

<= span lang=3D"EN-US">


<= br>



--000000000000874a250616b51439--