Out of curiosity, why doesn't this release get pulled from repositories. I understand all of the rationale behind no tests until the bug hits(and agree with it), i've been using mysql since 4.06, or 3.x i believe. I've never seen a "use [database]" case a segfault. I realize information_schema is special as is performance_schema. This is just a question, not a judgement.

Best,
Jeff

On Wed, Jun 5, 2019 at 4:15 AM Reinis Rozitis <r@roze.lv> wrote:

> It's also a bit scary that some people use this in production without testing. If
> there is really a simple way of getting a server segfault, than this should have
> come up on the test (before going into production).

It doesn't happen like that in software development - there are usually no tests before a particular bug/problem arises. Once it happens one can hope somebody will write a test for that (and add it to some continuous test framework) so it doesn’t return in future.

If you are directing it towards end-users - you can go through changelogs of every MySQL (upstream) and Mariadb (downstream) release and you'll see that if not every then every second has a major bug like crash / dataloss / corruption and what not else.
So you face the same scary choices when upgrading and when not. Asking for a user to test every aspect of a complicated piece of software as rdbm is a bit unrealistic.

rr

_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp