Thanks for the use case in MDEV-13115.

I've had a bit of a look at Oracle, Postgres, SQLite and have yet to see this supported feature on any UPDATE sql syntax. Can you see anything? Anything similar in other syntaxes like MERGE/UPSERT?

Sqlite has https://www.sqlite.org/lang_update.html which has a on-conflict ignore (https://www.sqlite.org/lang_conflict.html) which I don't think is the same thing because AFAIK sqlite is table level locks.

I've unfortunately not found another database implementing this, while the adaptation of the SELECT ... FOR UPDATE SKIP LOCKED syntax seems to be pretty wide. I did find however that MS-SQL implements a table hint: READPAST (https://docs.microsoft.com/en-us/sql/t-sql/queries/hints-transact-sql-table?view=sql-server-ver15) which seems to achieve the same goal.
For me it seems also just a logical extension of the SELECT ... FOR UPDATE SKIP LOCKED syntax, to be support on UPDATE and possibly DELETE (not required for my specific use-case). Since we already crossed the bridge of none-repeatable reads introduced by this syntax, why not support none-repeatable/deterministic update's(/delete's). I understand this violates many of the core foundations of a ACID database. But it seems to be very use-full in certain use-cases. And i do think when you know what your doing this allows for great features build upon.

Thanks for looking. It wasn't a prerequisite, just something to syntax model if it did exist.

Significant aspects of SELECT ... FOR UPDATE SKIP LOCKED are going to be reusable with this feature.

monty, serg do you have a syntax preference or objection to this feature?

what are the use cases?

see; https://jira.mariadb.org/browse/MDEV-13115?focusedCommentId=184792&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-184792
But generally i would say certain kind of queue's with concurrent workload.

DELETE SKIP LOCKED - would be nice for cleaning old rows. (Remove all rows not modified in last year etc)