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.96) (envelope-from ) id 1vlYeV-000hlx-1u for pgsql-general@arkaria.postgresql.org; Thu, 29 Jan 2026 20:30:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vlYeT-000mxr-1r for pgsql-general@arkaria.postgresql.org; Thu, 29 Jan 2026 20:30:06 +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.96) (envelope-from ) id 1vlYeS-000mxJ-2z for pgsql-general@lists.postgresql.org; Thu, 29 Jan 2026 20:30:06 +0000 Received: from hedgehog.birch.relay.mailchannels.net ([23.83.209.81]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vlYeP-000000004Vw-0cSi for pgsql-general@lists.postgresql.org; Thu, 29 Jan 2026 20:30:03 +0000 X-Sender-Id: dreamhost|x-authsender|stevej@stevej.name Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id A1E9122240D for ; Thu, 29 Jan 2026 20:29:57 +0000 (UTC) Received: from pdx1-sub0-mail-a235.dreamhost.com (100-123-102-161.trex-nlb.outbound.svc.cluster.local [100.123.102.161]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 4E00F2223E8 for ; Thu, 29 Jan 2026 20:29:57 +0000 (UTC) ARC-Seal: i=1; a=rsa-sha256; d=mailchannels.net; s=arc-2022; cv=none; t=1769718597; b=RwMoY++2euYpFm01+t5lIcVl2BKJMqCz9VznngO2ueu8p93JcDlx6Lhm4sUcvZyjU/h7WD 9YxX96t79HT3GIdMHG+lUNuUHI6zCp0PSzA+PeY5Sk708o5ElmLbtegU7lKtVz9G9U+N98 g6tjDFflnnw2yNrye+lEJqzvABKVy3x/cOK4geWGJi+2rsDZ5kfTytFhf5Eb9jydh8XNVX ZhVyz0jKyI7hruTZoLhfr1hM4dXjgLOoIaQlWGMRqUf7DqnsQBvXI7YMbDNBXWw92egaCZ M29lEr7Q2DOUcOoR9QOf0u/dW1um1Ed4B688Afq3mN+ANLloyHVqKQjZOj1Gkw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1769718597; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding:dkim-signature; bh=0TyVp/cfqKSTDZofbGK2Gl4Fll5FOQxBBk1Oac97qlE=; b=vmNSar1hHm2YmXwYA+XXNUOXresIoLmtqOswvU0ipOUjh8lO8usoCQoS+d5bakBYgdU4Oa Ij4T+De7v5pkq1YuRMnekhnDsVM08uBasiNWJajgXr2wnQnQLbrry5JgTo6SNQZTGFV7jz N4e0fnShOZZyidE1DPahfK37wkhFRGCUJXSB6EEsntm7ELpxOLK4WMQLm65bNGhELZq7Tp STq7ljmn825HsHNhjh/BNNgwNguWzMGvp7oBZ44qk2/CEKI9d/GwpTRVN0ox9JuNy8Tr27 OcY20R85BrjQYGYpjQpoTRvSeobDRFZTiBlmDLYNundqZv4k6N8abznYL8i97A== ARC-Authentication-Results: i=1; rspamd-5b979ccf89-qzxkn; auth=pass smtp.auth=dreamhost smtp.mailfrom=stevej@stevej.name X-Sender-Id: dreamhost|x-authsender|stevej@stevej.name X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|stevej@stevej.name X-MailChannels-Auth-Id: dreamhost X-Macabre-Drop: 2504ef805af449aa_1769718597507_359165600 X-MC-Loop-Signature: 1769718597507:280652302 X-MC-Ingress-Time: 1769718597507 Received: from pdx1-sub0-mail-a235.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.123.102.161 (trex/7.1.3); Thu, 29 Jan 2026 20:29:57 +0000 Received: from smtpclient.apple (unknown [73.240.31.54]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: stevej@stevej.name) by pdx1-sub0-mail-a235.dreamhost.com (Postfix) with ESMTPSA id 4f29jx0PbNzyrF for ; Thu, 29 Jan 2026 12:29:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stevej.name; s=dreamhost; t=1769718597; bh=0TyVp/cfqKSTDZofbGK2Gl4Fll5FOQxBBk1Oac97qlE=; h=Content-Type:Content-Transfer-Encoding:From:Date:Subject:To; b=mznawF4DkzefJM2WI4qXVkqAtwDy0JUfJGw9lyj3z2JiZ0YryyR4uWVhtd/EhqOfK 6ZkV0HqSPW+l9Jju7CzESleGRD+qMLnbEdB/IBi37RHx9niHLS5alf6SYn4vRZuEEV sGw/jlGNBoYXLI1ASDeNQV/MpeJSxxxsVeqjvRJmwz0xnwh1LC8n1jyAZGuLCotSiU VAs3HKvITpuWGZ8SIkWPX5P8yyCrOzw4y/aUnMMBUrUpxjookPGnd1N0m43LeKu/k9 P3B99aZQ0zvCn3y3JwXXrl1Q+4OdFihm7WbsPnH2ZZfTzQUV6Fb1QwDua/G/xipDZS E7Fd0gEbVoJ7Q== Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: "stevej@stevej.name" Mime-Version: 1.0 (1.0) Date: Thu, 29 Jan 2026 12:29:46 -0800 Subject: What happens if the socket lock file is deleted? Message-Id: To: pgsql-general@lists.postgresql.org X-Mailer: iPhone Mail (23C55) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk In software I have developed separately, I have noticed that most systems wi= ll periodically delete files within the temporary directory hierarchy that h= ave not been accessed recently, and that includes lock files for long runnin= g processes. I have never noticed the lock file associated with a postgreSQL= socket be missing though. Does PostgreSQL periodically touch the lock file so it won=E2=80=99t be dele= ted? Alternatively, does PostgreSQL simply re-create the lock file if it has= been deleted? I know the documentation says to never =E2=80=9Cmanually=E2=80= =9D=E2=80=99delete one of those lock files.=