On Wed, Mar 11, 2026 at 09:44:07AM -0700, Robert Pang wrote: > The current implementation of pg_promote() calculates a fixed number > of loop iterations based on the timeout value, assuming each loop > waits exactly 100 ms for the backend latch. However, if the backend > receives an unrelated signal (e.g., from > client_connection_check_interval), it wakes up early. These repeated, > unrelated wakeups cause the loop counter to deplete much faster than > intended, leading to a premature timeout.
It is true that we can do better here, and your proposal about having a more precise timeout calculation looks like a sensible improvement for this case. No objections regarding your patch. I would like to apply it on HEAD, if there are no objections. -- Michael
signature.asc
Description: PGP signature
