You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On some systems, the runner's query for work to do doesn't consistently return all of the rows it should, causing runs to be missed.
This query has been the same for years and the problem seems to be worse on more-recent versions of PostgreSQL, notably 15 on Debian 12 systems. It should work because the notifications sent to the runner happen after the transaction that produced them is committed.
Make the following improvements:
Remove notifications that aren't used (run_new being one)
Have the database send a run_ready notification with a row ID as the payload.
Change the runner to pick up those notifications and act on them individually if the start time is within the next iteration time
The text was updated successfully, but these errors were encountered:
On some systems, the runner's query for work to do doesn't consistently return all of the rows it should, causing runs to be missed.
This query has been the same for years and the problem seems to be worse on more-recent versions of PostgreSQL, notably 15 on Debian 12 systems. It should work because the notifications sent to the runner happen after the transaction that produced them is committed.
Make the following improvements:
run_new
being one)run_ready
notification with a row ID as the payload.The text was updated successfully, but these errors were encountered: