Lol what an absurd take. A transaction is a sequence of operations, not a single one, so even small tables can meet that threshold with enough query logic. I guess you're unfamiliar with medium to large datasets, but it's not uncommon to use the aggregate functions that SQL provides in real world situations, and on large tables that can easily reasonably exceed 1s. Toy my arse. Go play with yourself

Although this is no surprise tbh because apparently you don't understand why transactions are even necessary. Benchmarks shmenchmarks. Whether it works is more important.

I do not apologise for the downvote because this is smug shit only a junior would say

[–] Tja@programming.dev 1 points 1 day ago

Exactly my point. Wrong technology. If your operation takes more than 1s and you just accept it, you are not very good at your job. No worries, more job security for me!

I would recommend reading a few books, but given that you couldn't even read my first post about when to use transactions, it's futile.