public inbox for [email protected]
help / color / mirror / Atom feedFrom: Robert Haas <[email protected]>
To: Andres Freund <[email protected]>
Cc: [email protected]
Cc: Lukas Fittl <[email protected]>
Subject: Re: enable_timeout_every() and fin_time
Date: Tue, 3 Jan 2023 15:30:52 -0500
Message-ID: <CA+TgmoZvsehoTLyOodQeFvQsW85Yg_Rt3LSzXksYW_15oQs6Zw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CA+TgmobXKreG8=aTmW7bPKk4V=dcS3kFYXLhY_QHMzpNkKPO1w@mail.gmail.com>
<[email protected]>
On Tue, Jan 3, 2023 at 3:14 PM Andres Freund <[email protected]> wrote:
> Doesn't that discrepancy already exist as the code stands, because
> startup_progress_phase_start_time is also set in
> has_startup_progress_timeout_expired()?
I don't think it is, actually.
> I realize that was an example, but the
> issue seems broader: After the first "firing", the next timeout will be
> computed relative to an absolute time gathered in timestamp.c.
We're computing the time since the start of the current phase, not the
time since the last timeout. So I don't see how this is relevant.
--
Robert Haas
EDB: http://www.enterprisedb.com
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: enable_timeout_every() and fin_time
In-Reply-To: <CA+TgmoZvsehoTLyOodQeFvQsW85Yg_Rt3LSzXksYW_15oQs6Zw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox