June 2021 - discuss - lists.mariadb.org

[Maria-discuss] Galera 23.2.7 mariadb 5.5.33a msvc 1600 binaries available
by Yann Nayn 26 Apr '25

26 Apr '25

Binaries have been uploaded for both x86 and amd64 platforms. due to github file size limitations , the directories have been uploaded unarchived. for Win33 binaries , please checkout https://github.com/YannNayn/galera-mariadb-win32.git and for Win64(amd64) binaries (being uploaded/pushed): https://github.com/YannNayn/galera-mariadb-win64.git they are not recommended for a production environment. in the my.cnf file: _________ wsrep_provider=galera_smm.dll wsrep_sst_method=msqldump # percona xtrabackup will be tested soon _________ libevent and openssl(the provided binaries use respectively 2.1.3-alpha and 1.1.0-dev versions ) will be added next on github some limitations are stated on openssl website copied here for convenience: ____________ from http://www.openssl.org/ ____________ This software package uses strong cryptography, so even if it is created, maintained and distributed from liberal countries in Europe (where it is legal to do this), it falls under certain export/import and/or use restrictions in some other parts of the world. PLEASE REMEMBER THAT EXPORT/IMPORT AND/OR USE OF STRONG CRYPTOGRAPHY SOFTWARE, PROVIDING CRYPTOGRAPHY HOOKS OR EVEN JUST COMMUNICATING TECHNICAL DETAILS ABOUT CRYPTOGRAPHY SOFTWARE IS ILLEGAL IN SOME PARTS OF THE WORLD. SO, WHEN YOU IMPORT THIS PACKAGE TO YOUR COUNTRY, RE-DISTRIBUTE IT FROM THERE OR EVEN JUST EMAIL TECHNICAL SUGGESTIONS OR EVEN SOURCE PATCHES TO THE AUTHOR OR OTHER PEOPLE YOU ARE STRONGLY ADVISED TO PAY CLOSE ATTENTION TO ANY EXPORT/IMPORT AND/OR USE LAWS WHICH APPLY TO YOU. THE AUTHORS OF OPENSSL ARE NOT LIABLE FOR ANY VIOLATIONS YOU MAKE HERE. SO BE CAREFUL, IT IS YOUR RESPONSIBILITY. ________________________________________________ msvc 1600 redistributables SP1 need to be installed/available on the target machine: vcredist_x86.exe : http://www.microsoft.com/en-us/download/details.aspx?id=8328 vcredist_x64.exe : http://www.microsoft.com/en-us/download/details.aspx?id=13523 MSys binaries are provided and msqld.bat should then be used instead of mysqld.exe (e.g. mysld.bat --console --wsrep_cluster_address=gcomm:// ) in order to have a working sh shell(cygwin has been proved to do it as well) Please note that oqgraph is disabled (boost trunk is used , that is 1.55) Comments and suggestions are welcome.

4 3

[Maria-discuss] Differences between MariaDB packages
by William Edwards 27 Jun '21

27 Jun '21

Hello, I recently discovered a bug in my MariaDB deployment process. I have two Ansible tasks that respectively add the downloads.mariadb.org Debian repo, and install mariadb-server-10.*. I forgot to add 'update_cache: yes' to the repo add task, so incidentally mariadb-server-10.* was actually installed from the Debian repo. I have seen the following differences between the mariadb-server-10.* packages: - Packages from Debian repo only come with the 'root@localhost' user. Packages from MariaDB repo come with the users 'root@localhost', 'root@::1' and 'root(a)127.0.0.1'. - Packages from Debian repo don't come with 'debian-sys-maint@localhost' user. Instead, the 'root' user is used in /etc/mysql/debian.cnf - Packages from Debian repo use DebianAlternatives for my.cnf. Packages from MariaDB repo also come with a more advanced my.cnf, e.g. 'bind-address = 127.0.0.1' is set - not being able to remotely connect is how I discovered this bug on my side. - Packages from MariaDB repo come with package configuration (specifically: setting root password). Q: I'm wondering if anyone has a more complete list of differences between these packages (the above is just what I've observed from fixing issues due to this bug). I don't know if the Debian maintainers for this package branch off a package by MariaDB, so I posted this here, but please let me know if I would be better off posting this on a Debian mailing list. TIA. With kind regards, William Edwards

3 2

[Maria-discuss] OpenSSL 3.0 support
by Lukas Javorsky 17 Jun '21

17 Jun '21

Hi, We've created two Jira tickets for the OpenSSL 3.0 support, however, we didn't really get a response or any detailed information from you about it. Connector-c: https://jira.mariadb.org/browse/CONC-503 Server: https://jira.mariadb.org/browse/MDEV-25785 It's our big concern to support this ASAP because we are aiming to support OpenSSL version 3.0 in the RHEL-9 which is coming soon. Our mission in RHEL-9 is to aim for the newest software version because we are going to support this OS for more than 10 years, and the major changes should be done in the beginning. We would like to know your opinion about this so we can maybe try to help you in some way. Please let us know what you think about it. Thank you and have a nice day -- S pozdravom/ Best regards Lukáš Javorský Associate Software Engineer, Core service - Databases Red Hat <https://www.redhat.com> Purkyňova 115 (TPB-C) 612 00 Brno - Královo Pole ljavorsk(a)redhat.com <https://www.redhat.com>

2 1

[Maria-discuss] Problem with mariabackup
by Riccardo Brunetti 17 Jun '21

17 Jun '21

Hello. We are using the mariabackup tool to stream to a remote server the backup of our databases. We are having some issue because in the middle of the operation the db server stops responding for many minutes until we ultimately kill the mariabackup process. During the lock, we can see the following: > MariaDB [(none)]> show processlist; > > +--------+----------------------------+-----------------+--------------------------+---------+------+------------------------------+------------------------------------------------------------------------------------------------------+----------+ > > | Id | User | Host | db | Command | Time | State | Info | Progress | > > +--------+----------------------------+-----------------+--------------------------+---------+------+------------------------------+------------------------------------------------------------------------------------------------------+----------+ > > | 3 | system user | | NULL | Daemon | NULL | InnoDB purge worker | NULL | 0.000 | > > | 4 | system user | | NULL | Daemon | NULL | InnoDB purge worker | NULL | 0.000 | > > | 1 | system user | | NULL | Daemon | NULL | InnoDB purge coordinator | NULL | 0.000 | > > | 2 | system user | | NULL | Daemon | NULL | InnoDB purge worker | NULL | 0.000 | > > | 5 | system user | | NULL | Daemon | NULL | InnoDB shutdown handler | NULL | 0.000 | > > | 274355 | root | localhost:42512 | NULL | Sleep | 407 | | NULL | 0.000 | > > | 297631 | udaww4uw_gsut | localhost:39784 | udaww4uw_gsprod | Query | 17 | Waiting for global read lock | UPDATE `wp_litespeed_crawler` SET reason = CONCAT( SUBSTRING_INDEX( reason, ',', 0 ), '200', SUBSTRI | 0.000 | > > | 302083 | ud4k9xsm_pres633 | localhost | ud4k9xsm_pres633 | Query | 47 | Waiting for global read lock | DELETE FROM `ps4d_marketplace_product_action` > > WHERE `id_product` = 7356 AND `id_lan | 0.000 | > > | 302391 | udaww4uw_gsut | localhost:50748 | udaww4uw_gsprod | Query | 46 | Waiting for global read lock | INSERT INTO wp_post_views (id, type, period, count) > > VALUES (62075, 3, '2021', 1) > > ON DUPLIC | 0.000 | > > | 302395 | uqlugtoj_enedina.it | localhost | uqlugtoj_enedina | Query | 44 | Waiting for global read lock | UPDATE `wp_options` SET `option_value` = '1623829414' WHERE `option_name` = '_transient_timeout_wc_r | 0.000 | > > | 302404 | udlah5r1_remigio | localhost:50782 | udlah5r1_vtiger71 | Query | 44 | Waiting for global read lock | insert into vtiger_pbxmanager(pbxmanagerid,direction,callstatus,starttime,endtime,totalduration,bill | 0.000 | > > | 302431 | utlmb6ko_6M0oD0 | localhost | utlmb6ko_6M0oD0 | Query | 38 | Waiting for global read lock | UPDATE `wp_options` SET `option_value` = '1623743080' WHERE `option_name` = 'action_scheduler_lock_a | 0.000 | > > | 302432 | uml1gkxr_58IJ3 | localhost:50836 | uml1gkxr_prod | Query | 38 | Waiting for global read lock | UPDATE `wp_options` SET `option_value` = 'a:13835:{i:1226;s:32:\"ab7050de2954be1e369e358a15a17c48\"; | 0.000 | > > | 302433 | uml1gkxr_58IJ3 | localhost:50838 | uml1gkxr_prod | Query | 38 | Waiting for global read lock | UPDATE `wp_options` SET `option_value` = 'a:13835:{i:1226;s:32:\"ab7050de2954be1e369e358a15a17c48\"; | 0.000 | > > | 302440 | uqtx0c94_giorgio | localhost:50848 | uqtx0c94_due | Query | 38 | Waiting for global read lock | UPDATE `wp_options` SET `option_value` = '[]' WHERE `option_name` = '_transient_adsforwp_transient_a | 0.000 | > > | 302473 | uw6vnwff_helpdesk | localhost:50932 | uw6vnwff_helpassist | Query | 30 | Waiting for global read lock | INSERT INTO ost_syslog SET created=NOW(), updated=NOW() ,title='DB Error #1205',log_type='Error',log | 0.000 | At the same time, we see messages like these in the system log: > Executing FLUSH NO_WRITE_TO_BINLOG TABLES... > > Executing FLUSH TABLES WITH READ LOCK... This is the command we launch to backup data: > mariabackup --backup --stream=xbstream --user=root --extra-lsndir=${BCKDBDIR} -u${MYSQLUSER} -p${MYSQLPW} -H ${MYSQLHOST}" Is it somehow an expected behavior (some of the db are quite heavily used)? How can we avoid those locks? Thanks Riccardo

3 7

[Maria-discuss] Disable Some Operators in Fulltext Boolean mode
by Samuel Lorch 12 Jun '21

12 Jun '21

Hello, I am using MariaDB in a Project and to Allow users to Search the Data we use Fulltext Indexes, as you cannot make a Fulltext Index across multiple tables we have multiple match against statements and are Combining them with OR. The Problem is that the Natural Language Mode only Matches Full Words and not Partial ones. The Solution is Boolean Mode where you can append a * to a word to allow 0 or more characters. But Boolean Mode also Brings Other Operators. These other Operator can Behave Unexpectedly for The User when Combining Multiple Match Against Statements With OR. Using the "ft_boolean_syntax" variable one can change the characters used for these operators but this is limited to ASCII characters below 127. I suggest That we add a special character that disables a operator. What do you think about this? Or do you See a different Solution? Regards, Samuel

1 0

[Maria-discuss] DBSeeder Version 2.9.0
by Walter Weinmann 08 Jun '21

08 Jun '21

We are happy to announce that version 2.9.0 of DBSeeder ( https://github.com/KonnexionsGmbH/db_seeder) is now available for general use. DBSeeder also supports the latest version of MariaDB Server available on DockerHub (10.6.1).

2 2