Re:Why Uber Engineering Switched from Postgres to MySQL (2016)
by BitPirate on Saturday February 27, 2021 @09:55AM
(#26285210)
One can still complain about mysqls dumb defaults.
https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.ht...
"Hey, let's just not act transactional on a timeout by default"
Re:Why Uber Engineering Switched from Postgres to MySQL (2016)
by evanelias on Saturday February 27, 2021 @10:54AM
(#26285604)
That default is sensible. You're making it sound like this setting applies to all "timeouts" regardless of type. That is not the case.
This setting applies to lock-wait timeouts. The default value allows applications to decide on the correct course of action: either re-try just the statement that timed out (without having to re-do the previous parts of the transaction), or rollback the transaction.
The application still receives an error on the timeout regardless of this setting. The database doesn't automatically commit the previous statements in the transaction regardless of this setting.
Much of your MySQL complaint is not a MySQL issue, but a config issue.
And yes, powerful config options are good, not bad.