Re: pgsql: TAP tests: check for postmaster.pid anyway when "pg_ctl start" f

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: TAP tests: check for postmaster.pid anyway when "pg_ctl start" f
Date: 2022-02-11 00:57:20
Message-ID: 1953533.1644541040@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Should we take the danger of postmaster dying without cleaning up the pid 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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Christoph Berg 2022-02-11 09:48:11 Re: pgsql: Add TAP test to automate the equivalent of check_guc
Previous Message Andres Freund 2022-02-10 22:52:54 Re: pgsql: TAP tests: check for postmaster.pid anyway when "pg_ctl start" f