Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-committers-owner+archive@lists.postgresql.org>)
	id 1nIKFh-0003Sr-EM
	for pgsql-committers@arkaria.postgresql.org; Fri, 11 Feb 2022 00:57:33 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-committers-owner+archive@lists.postgresql.org>)
	id 1nIKFf-0004b5-QO
	for pgsql-committers@arkaria.postgresql.org; Fri, 11 Feb 2022 00:57:31 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nIKFf-0004aw-JN
	for pgsql-committers@lists.postgresql.org; Fri, 11 Feb 2022 00:57:31 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nIKFZ-00087n-9U
	for pgsql-committers@lists.postgresql.org; Fri, 11 Feb 2022 00:57:30 +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 21B0vKla1953534;
	Thu, 10 Feb 2022 19:57:20 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Noah Misch <noah@leadboat.com>, Thomas Munro <thomas.munro@gmail.com>,
        pgsql-committers <pgsql-committers@lists.postgresql.org>
Subject: Re: pgsql: TAP tests: check for postmaster.pid anyway when "pg_ctl
 start" f
In-reply-to: <20220210225254.pds2dowte5yophmr@alap3.anarazel.de>
References: <E1nAIWI-0006et-HW@gemulon.postgresql.org>
 <CA+hUKGKV6fOHvfiPt8=dOKzvswjAyLoFoJF1iQXMNpi7+hD1JQ@mail.gmail.com>
 <855583.1642687119@sss.pgh.pa.us> <867290.1642689136@sss.pgh.pa.us>
 <20220120192736.msyesvdlljn6tptw@alap3.anarazel.de>
 <926839.1642708567@sss.pgh.pa.us> <1075553.1642717844@sss.pgh.pa.us>
 <20220210023537.GA3222837@rfd.leadboat.com>
 <1709793.1644523137@sss.pgh.pa.us>
 <20220210223806.ikpf57pz2ilamqam@alap3.anarazel.de>
 <20220210225254.pds2dowte5yophmr@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Thu, 10 Feb 2022 14:52:54 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1953532.1644541040.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 10 Feb 2022 19:57:20 -0500
Message-ID: <1953533.1644541040@sss.pgh.pa.us>
List-Id: <pgsql-committers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-committers@lists.postgresql.org>
List-Owner: <mailto:pgsql-committers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-committers>
Archived-At: 
 <https://www.postgresql.org/message-id/1953533.1644541040%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> Should we take the danger of postmaster dying without cleaning up the pi=
d file
> and then another process reusing that pid serious? That obviously could =
make
> pg_ctl wait until timeout.

I'm under the impression that Unixen try not to recycle PIDs within
a short interval.  So I'm not that worried about this.  (Also, since
we treat EPERM like ESRCH, conflicting PIDs belonging to other user
IDs won't matter anyway.)

			regards, tom lane