Gabriele Svelto (gabriele.svelto.delete@this.gmail.com) on February 3, 2020 12:47 am wrote:
> I see that you were wrong about the most used DB in existence and
> you hand-wave it away because it doesn't fit your narrative.

Google for "MySQL OOM", "MySQL memory overcommit", etc and you will find what you want, but MySQL/MariaDB are not in the same class of other RDBMSes.

> First of all you don't get to pick which one is a "real" database
> and which one is not in order to prove your point. The all are.

Although subjective, it is very simple to separate MySQL/MariaDB from real databases, in a real database you can query your data in efficient ways, with simple and readable text, at least most of the time, and the software will choose an appropriate algorithm to the task, will try to make data access faster, will try to make good use of resources, make manipulation of data consistent, PostgreSQL, Oracle, SQL Server, DB2, Sybase, all does this, MySQL/MariaDB implements a trivial set of algorithms to look like a database.

> Secondly the amount of configuration options shown in the links you posted seems to contradict this claim.

The user MAY tune the server for his specific need, don't HAVE to and documentation suggest he SHOULD NOT, so what?

> Even Microsoft's SQL server requires explicit configuration to avoid out-of-memory conditions in certain
> modes. That's particularly ironic because the documentation goes to great lengths to claim that in regular
> mode it shouldn't need any kind of setup and will automatically scale memory usage up and down on demand.

SQL Server In-Memory OLTP

Did you notice the "In-Memory" expression when linking?

> Funny thing also: SQL server doesn't detect low memory conditions because you start
> getting NULL's from malloc() calls, it uses memory resource notifications.

I never looked at SQL Server source code, but I guess there is no malloc at all, also I am pretty sure that there are checks at all calls to VirtualAlloc.