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 1rz1Xc-001Yew-1m for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 21:49:36 +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 1rz1Xa-000OPL-8r for pgsql-general@arkaria.postgresql.org; Mon, 22 Apr 2024 21:49:34 +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 1rz1XZ-000OP7-B7 for pgsql-general@lists.postgresql.org; Mon, 22 Apr 2024 21:49:33 +0000 Received: from fout1-smtp.messagingengine.com ([103.168.172.144]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rz1XW-002Pdv-79 for pgsql-general@postgresql.org; Mon, 22 Apr 2024 21:49:32 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfout.nyi.internal (Postfix) with ESMTP id 9CB07138023F; Mon, 22 Apr 2024 17:49:27 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 22 Apr 2024 17:49:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1713822567; x=1713908967; bh=+8Jrfonc0XCmiINkg12O7ANgNPzND9oGiXxT1vY/+MU=; b= ix6rGHB3wMnN//CI3Myp/26YNlwFLF+838xM2dX52B46B9XlG5rP5luAAg1SAd6Y bDYO1Bj1+loO24A3Jnri907ZZTgXna7BH/yTs6DluX1xJGMfPPIEizc05u3C8//6 VNOprdsBVuQtfOO3JFUA5AZuQsk7PR+owD7sf8kUlaum5ob9+rApJF2mDngwjQDN huV1QJ6D2rQhmm8CGHfhul97J98w+1Y/NwHNCwvRcckD8p4EOcOvLbBjHyZsgf38 bjhc63TY83h6mMtd0V9fIvtpXDCe22Wmyqhmw0Xiebe9cIiF+P2nXZ3mKDQp5Z76 umvMflhqqRIRM8vL8dBh0w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1713822567; x= 1713908967; bh=+8Jrfonc0XCmiINkg12O7ANgNPzND9oGiXxT1vY/+MU=; b=N 9thD2PCusLHForqcc9+AmiKP6UCnnrnEa7ekQEvtL9VFCH47Ay6TGERume8FAP1N JeIH4boJuOpRJ8Jj4HLTRMaIrptlOzAPINd5+Wy7ZogJstAZLXO4LHAw93G6E00u TrfQt36av9LEGEN5w1lJbwkZJS5+QmZtSw1SE0OGzTGr/TBgX4H3Ij32vLSGBI4P OxDNAS+t0NQdaW5j2ur3A4TopsFxLaWYIGWQ9UasaIVf+r2VuT9WpoPeYNu/Q7mt Mo6BxSV07ibSwsVe3Ci75dqymXf88FOueeu8MSLjSjo4mdhflOmClyPqcG2+SadS D/1fq+Icgh7yhKX1dD3zw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudeltddgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepfeegfeeiuedtgffgteeggfehkeejheetieeliefg teeikeejvdeiveeigfehvedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 22 Apr 2024 17:49:26 -0400 (EDT) Message-ID: <2015f756-b188-4840-922d-6f927997ab51@aklaver.com> Date: Mon, 22 Apr 2024 14:49:26 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: issue with reading hostname To: Atul Kumar Cc: pgsql-general References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 4/22/24 14:37, Atul Kumar wrote: > Can we edit the socket to change the hostname in it ? On Ubuntu 22.04 install, given: srwxrwxrwx 1 postgres postgres 0 Apr 22 14:01 .s.PGSQL.5432= -rw------- 1 postgres postgres 68 Apr 22 14:01 .s.PGSQL.5432.lock The contents of .s.PGSQL.5432.lock(the file that indicates a Postgres instance has a lock on the socket) are: 862 /var/lib/postgresql/15/main 1713795311 5432 /var/run/postgresql There is no hostname to be changed as you are working with a local socket. > > Regards. > > On Tue, Apr 23, 2024 at 2:41 AM Ron Johnson > wrote: > > On Mon, Apr 22, 2024 at 4:14 PM Atul Kumar > wrote: > > 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();' > > > If you installed from the PGDG repository (possibly also the CENTOS > repos, but I'm not sure), then the domain socket also lives in : > /var/run/postgresql > > * I find that more expressive than /tmp. > * No need to specify the host when using sockets. > * Using a socket name makes parameterizing the hostname easier in > scripts. > > -- Adrian Klaver adrian.klaver@aklaver.com