Some of the MariaDB 10.1 versions trivially corrupted themselves by just loading them up with writes a bit, no crashes or power issues involved.
One of the 10.6 versions had (has?) a bug where a connection sometimes simply does not die ever, even after disconnecting and killing the query using the KILL sql command, so it never releases its slot (which matters if you have lots of connections), although to be fair I've only hit that once since we upgraded to 10.6.
Frankly I prefer MySQL and friends over Postgres simply because that's what I always used and I find it familiar (plus I don't like the process based concurrency that Postgres has, while I haven't really tried it to see if it matters, process creation is fairly expensive in Windows to use as a concurrency mechanism and limits the numbers of connections a lot more than threads), but let's not deny reality here, MySQL has never been rock-solid and a glance at its source code should be enough to tell you why.
As for your disregard for performance issues, it's hard to say if it's warranted without knowing the numbers and the load profile but it's probably preferable to spend the time to test it properly than having to fix everything in a hurry later with customers screaming at you over the phone.
Plus I like programs built to be snappy and fast, a good practice that sadly has been lost to time.
One of the 10.6 versions had (has?) a bug where a connection sometimes simply does not die ever, even after disconnecting and killing the query using the KILL sql command, so it never releases its slot (which matters if you have lots of connections), although to be fair I've only hit that once since we upgraded to 10.6.
Frankly I prefer MySQL and friends over Postgres simply because that's what I always used and I find it familiar (plus I don't like the process based concurrency that Postgres has, while I haven't really tried it to see if it matters, process creation is fairly expensive in Windows to use as a concurrency mechanism and limits the numbers of connections a lot more than threads), but let's not deny reality here, MySQL has never been rock-solid and a glance at its source code should be enough to tell you why.
As for your disregard for performance issues, it's hard to say if it's warranted without knowing the numbers and the load profile but it's probably preferable to spend the time to test it properly than having to fix everything in a hurry later with customers screaming at you over the phone.
Plus I like programs built to be snappy and fast, a good practice that sadly has been lost to time.