You can avoid buffer overflows in C by using a library that's got safe strings.
Does that make C safe? Nope.
The Windows NT architecture has an enormously rich security mechanism that can allow arbitrarily granular security statements to be made about almost everything. But the default policy until Windows 7 was "pretend you're Windows 95".
Did that make Windows more secure than Unix? Nope.
Comments
The baseline is what counts.
You can avoid buffer overflows in C by using a library that's got safe strings.
Does that make C safe? Nope.
The Windows NT architecture has an enormously rich security mechanism that can allow arbitrarily granular security statements to be made about almost everything. But the default policy until Windows 7 was "pretend you're Windows 95".
Did that make Windows more secure than Unix? Nope.
The baseline is what counts.
The baseline (reading as default configuration) is the only thing that counts? Then Postgres is unusable for any reasonably sized dataset.
Of course, so is Oracle, SQL Server, and every other database known to man.
You have to tailor the configuration of any database server to meet your needs. MySQL is no different in this regard.
My need is for a database that doesn't silently corrupt my data.
MySQL is different in this regard.