[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-hackers
Subject:    Re: when the startup process doesn't (logging startup delays)
From:       Robert Haas <robertmhaas () gmail ! com>
Date:       2021-10-29 18:44:38
Message-ID: CA+TgmoabzuDusgH6Mp-b+znfrHCdsrbAv2H1=zPsDf2gYvGsRA () mail ! gmail ! com
[Download RAW message or body]

On Fri, Oct 29, 2021 at 9:10 AM Nitin Jadhav
<nitinjadhavpostgres@gmail.com> wrote:
> > I think you're wrong. If we did that, the previous timer could fire
> > right after we set startup_progress_timer_expired = false, and before
> > we reschedule the timeout. It seems annoying to have to disable the
> > timeout and immediately turn around and re-enable it, but I don't see
> > how to avoid the race condition otherwise.
>
> Right. There is a possibility of race conditions. In that case the
> above changes look good to me.

Committed.

-- 
Robert Haas
EDB: http://www.enterprisedb.com


[prev in list] [next in list] [prev in thread] [next in thread]