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 1vlxNK-005gtP-12 for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Jan 2026 22:54:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vlxMG-006ZOr-2g for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Jan 2026 22:52:57 +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 1vlqup-005NhT-0g for pgsql-bugs@lists.postgresql.org; Fri, 30 Jan 2026 16:00:12 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vlqun-00000000DkW-03FE for pgsql-bugs@lists.postgresql.org; Fri, 30 Jan 2026 16:00:11 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=rUQXusehRNhoQANBC0UKECJxqCtQgyrG9Z0ain8ZcC8=; b=20KXTIiSAI0n55r2xEd2XNb/Gd nqQiuoWtOx0AoImxcsbgNgIKtpk1o2qInDKgmhzFXK16i+bwGgHYQsCimq1TaXpyvNVb8btY8QT4R CXI8vV2yLhM7ju2sp8MWOjtDDk2Od565mUTpXIubpV0wdATaQsB6UitXUVFPvbewzZL2b6QeKZg1u jXFAKXhtJVhcXD9i0rNXrG4/4v2B45QNHNYdXtD5mG8fU2+g2IkftzL22E4g5wrJbKHfJcNzGeiuF 4PXG2xzKKoCHCgmWodNgp2ViQ7l5iXkFrQ6sDUZfWXPl5wdkOpczWVHPq+IS9DUuHkRZt1Ek0wg8d I2x5vHHw==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vlquk-000SYw-0E for pgsql-bugs@lists.postgresql.org; Fri, 30 Jan 2026 16:00:07 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vlquh-000uTK-0A for pgsql-bugs@lists.postgresql.org; Fri, 30 Jan 2026 16:00:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19391: pg_ctl: the PID file "/xxxx/postmaster.pid" is empty To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: d.kovalenko@postgrespro.ru Reply-To: d.kovalenko@postgrespro.ru, pgsql-bugs@lists.postgresql.org Date: Fri, 30 Jan 2026 15:59:18 +0000 Message-ID: <19391-fb300ee2c6fa87b5@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19391 Logged by: Dmitry Kovalenko Email address: d.kovalenko@postgrespro.ru PostgreSQL version: 17.7 Operating system: Linux Description: =20 Hello, My test framework uses "pg_ctl status ..." to detect a state of Postgres instance - uninitialized, stopped, running. Time from time, it returns the error - pg_ctl: the PID file "/xxxx/postmaster.pid" is empty https://github.com/postgrespro/testgres/issues/329 I think, postgres and pg_ctl do not should create a such issues. Thanks&Regards, Dmitry Kovalenko