Re: low wal_retrieve_retry_interval causes missed signals on Windows

2023-01-11 Thread Nathan Bossart
On Wed, Jan 11, 2023 at 04:40:14PM -0800, Andres Freund wrote: > On 2023-01-11 15:26:45 -0800, Nathan Bossart wrote: >> On Wed, Jan 11, 2023 at 12:48:36PM -0800, Andres Freund wrote: >> > Given that we check for interrupts in other parts of recovery with >> > HandleStartupProcInterrupt(), which doe

Re: low wal_retrieve_retry_interval causes missed signals on Windows

2023-01-11 Thread Andres Freund
Hi, On 2023-01-11 15:26:45 -0800, Nathan Bossart wrote: > On Wed, Jan 11, 2023 at 12:48:36PM -0800, Andres Freund wrote: > > Given that we check for interrupts in other parts of recovery with > > HandleStartupProcInterrupt(), which doesn't interact with latches, isn't the > > actual bug that Handl

Re: low wal_retrieve_retry_interval causes missed signals on Windows

2023-01-11 Thread Nathan Bossart
On Wed, Jan 11, 2023 at 12:48:36PM -0800, Andres Freund wrote: > Given that we check for interrupts in other parts of recovery with > HandleStartupProcInterrupt(), which doesn't interact with latches, isn't the > actual bug that HandleStartupProcInterrupt() doesn't contain the same black > magic th

Re: low wal_retrieve_retry_interval causes missed signals on Windows

2023-01-11 Thread Andres Freund
Hi, On 2023-01-10 22:11:16 -0800, Nathan Bossart wrote: > The attached patch fixes this by always calling WaitLatch(), even if > wal_retrieve_retry_interval milliseconds have already elapsed and the > timeout is 0. It doesn't seem right to call WaitLatch() just for that purpose - nor necessarily