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 ) id 1mVdz1-0005DA-9v for pgsql-hackers@arkaria.postgresql.org; Wed, 29 Sep 2021 18:07:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mVdz0-00075L-89 for pgsql-hackers@arkaria.postgresql.org; Wed, 29 Sep 2021 18:07:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mVdz0-00075D-0F for pgsql-hackers@lists.postgresql.org; Wed, 29 Sep 2021 18:07:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mVdyx-00053c-LP for pgsql-hackers@postgresql.org; Wed, 29 Sep 2021 18:07:05 +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 18TI6uiE2992586; Wed, 29 Sep 2021 14:06:56 -0400 From: Tom Lane To: Alvaro Herrera cc: Robert Haas , Nitin Jadhav , Justin Pryzby , Michael Paquier , Bharath Rupireddy , Andres Freund , Stephen Frost , Magnus Hagander , Thomas Munro , "pgsql-hackers@postgresql.org" Subject: Re: when the startup process doesn't (logging startup delays) In-reply-to: <202109291749.ejyaab7wazx7@alvherre.pgsql> References: <202109291749.ejyaab7wazx7@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Wed, 29 Sep 2021 14:49:31 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2992584.1632938816.1@sss.pgh.pa.us> Date: Wed, 29 Sep 2021 14:06:56 -0400 Message-ID: <2992585.1632938816@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alvaro Herrera writes: > On 2021-Sep-29, Robert Haas wrote: >> Well, this was my suggestion, because if you don't do this, you get >> drift, which I think looks weird. Like the timestamps will be: >> >> 13:41:05.012456 >> 13:41:15.072484 >> 13:41:25.149632 >> >> ...and it gets further and further off as it goes on.' > Right ... I actually *expect* this drift to occur. Maybe people > generally don't like this, it just seems natural to me. Are there other > opinions on this aspect? FWIW, I agree with Robert that it's nicer if the timeout doesn't drift. There's a limit to how much complexity I'm willing to tolerate for that, but it doesn't seem like this exceeds it. The real comment I'd have here, though, is that writing one-off code for this purpose is bad. If we have a need for a repetitive timeout, it'd be better to add the feature to timeout.c explicitly. That would probably also remove the need for extra copies of the timeout time. regards, tom lane