On Fri, Oct 29, 2021 at 7:37 AM Nitin Jadhav <nitinjadhavpostg...@gmail.com> wrote: > ereport_startup_progress() logs a message. So I feel just setting > 'startup_progress_timer_expired' to false in > begin_startup_progress_phase() would work. Please correct me if I am > wrong.
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. -- Robert Haas EDB: http://www.enterprisedb.com
