MariaDB 10.3 created with a "-log" version

Question

Hi, I have created a MariaDB server in the West Europe region. I have selected version 10.3

Performance Configuration: General Purpose, 2 vCore(s), 5 GB

The server has been created using the version 10.3.23-MariaDB-log.

show global variables like '%version%';  
+-----------------------------------+------------------------------------------+  
| Variable_name                     | Value                                    |  
+-----------------------------------+------------------------------------------+  
| in_predicate_conversion_threshold | 1000                                     |  
| innodb_version                    | 10.3.23                                  |  
| protocol_version                  | 10                                       |  
| slave_type_conversions            |                                          |  
| system_versioning_alter_history   | ERROR                                    |  
| system_versioning_asof            | DEFAULT                                  |  
| version                           | 10.3.23-MariaDB-log                      |  
| version_comment                   | MariaDB Server                           |  
| version_compile_machine           | x64                                      |  
| version_compile_os                | Win64                                    |  
| version_malloc_library            | system                                   |  
| version_source_revision           | 7a97b525ea6a3ff619e8d156bf11bfe5b3acf8c2 |  
| version_ssl_library               | YaSSL 2.4.4                              |  
+-----------------------------------+------------------------------------------+  

The -log part is enabling the binary logs, which I need to be disabled.

show global variables like 'log_bin';  
+---------------------------------+------------------------------+  
| Variable_name                   | Value                        |  
+---------------------------------+------------------------------+  
| log_bin                         | ON                           |  
+---------------------------------+------------------------------+  

Is there a way to define the MINOR version or to change the server settings in order to set the log_bin to OFF?

I have tried what is suggested here including using init-connect without success (log_bin is a read-only variable). I have read in other forums that I should modify the configuration files and restart the server, but this does not seem to be an option in Azure DB for MariaDB.

Has anyone noticed/faced a similar issue?

Answer 1

Hi @luispinedamx , below is the verbatim we received from the product team:

"Recently, we change the default storage platform for MariaDB. As part of this change we enable binary log by default and it cannot be disabled and it is required for backups and recovery of the managed service. As a result, we do not allow disabling of binary logs from service. This is by design."

However, could you please let us know the intent behind disabling it? This way we can check how could they possibly help us with your concern.

Answer 2

Hi @AnuragSharma-MSFT , sorry to write it as an answer but I cannot submit my comment ('Submit' button not working)

Yes sure, let me elaborate on my issue, might be useful for the community:

In our application we use sql triggers. Everything went fine as long as the log_bin were OFF, as in all of our previous servers. Now, with the log_bin ON, we get this message when a trigger gets activated:

You do not have the SUPER privilege and binary logging is enabled (you might want to use the less safe log_bin_trust_function_creators variable)

We did set to ON the suggested variable log_bin_trust_function_creators to test as a workaround and it works, but this is NOT safe because it might have unintended consequences as explained in MariaDB's documentation, so using this variable is not an option

For security, we certainly cannot give SUPER privileges to the user either.

The problem is: being able to continue to execute our triggers, without enabling unsafe features.

Thanks,
Luis