Conversation
| @@ -0,0 +1,2 @@ | |||
| CREATE INDEX IF NOT EXISTS IDX_IDEMPOTENT_ACTION_TYPE_CLIENT | |||
There was a problem hiding this comment.
I was just googling to see if there's a mariadb equivalent of concurrently - looks like adding ALGORITHM=INPLACE LOCK=NONE may do the trick?
| "DELETE FROM idempotent_action " + | ||
| "WHERE type = :type " + | ||
| " AND client = :client " + | ||
| "ORDER BY created_at ASC " + |
There was a problem hiding this comment.
This was a good spot - it's not necessary for this to be deterministic!
|
/wise-bot sync-codeowners |
|
These are all the things I can do:
|
|
/wise-bot run-action sync-codeowners |
|
🔴 No |
❓ Context
On applications with large
idempotent_actiontables,deleteByTypeAndClientcan be optimised by removing the need to sort actions before delete🚀 Changes
deleteByTypeAndClientqueriesdeleteByTypeAndClientqueries to let db return/delete records in natural order without the overhead of sortingConsiderations
Actions will no longer be deleted oldest first