maria-discuss team mailing list archive

[Reindl Harald <h.reindl@xxxxxxxxxxxxx>]

Am 03.09.19 um 09:50 schrieb Benoit Plessis:
>> Am 02.09.19 um 19:38 schrieb Faustin Lammler:
>>> I am truly sorry by the issue you are facing, but giving us *in
>>> your first post* the version and the OS would have been more
>>> productive IMHO
>>
>> don't get me wrong *but* i find it insulting when someone accueses me
>> that i jump from some random completly outdated version to 10.3.x and
>> then come up with "but why where the no warning in 10.0/10.1 that
>> something disappears in 10.3"
>>
>> that's what i call common sense on both sides
>>
>> anyways, the real problem i have with your response is that you jumped
>> into two posts between me and a core developer and stripped everything
>> relevant while  i showed a complete restart log without any mentioning
>> of "innodb_support_xa" at all and asked where the warning is the core
>> developer talked about
> 
> No he did not, i did, and for that i am mildly sorry, and only mildly
> because of the tone you used since the beginning of the discussion but i
> should have keep my calm.

yes

> As for your 'kind suggestion' of handling deprecated/unknown option i
> personnally strongly disagree, some of mysql/mariadb options have real
> impact and "physical" consequences on the database, preventing it to
> start because of setting not handled is way safer that ignoring them and
> only putting a warning in the logs.

"-DPLUGIN_PERFSCHEMA=NO" is the same as "performance-schema=0" is doing
the same while "performance-schema=0" on a binary with the built with
the first one prevents mysqld from start

when i *explicit disable* some bloatware crap it's missing exitence is
not a hard error

that is idiotic, the same for partitioning and so on

any fucking option from the documentation must not trigger hard errors
when it exists in a config file, no matter what - period