March 2022 - 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] Repos empty?
by William Edwards 15 Aug '22

15 Aug '22

Hello, The Debian repos @ https://mariadb.org/download/?t=repo-config don't seem to contain any packages and no Release file anymore. Last updated yesterday at 18:41 (IDK which timezone). E.g. http://ams2.mirrors.digitalocean.com/mariadb/repo/10.3/debian/dists/buster/… (the issue isn't with this specific mirror). When choosing a repo on mariadb.org, the error "An error occured. The mirrors could not be loaded." is shown. -- With kind regards, William Edwards

2 4

[Maria-discuss] mysql 5.5 client vs mariadb 10 server
by Oliver 22 Mar '22

22 Mar '22

Hi, I'm sorry for the question if it is clear that it isn't possible. I'm trying connect from a mysql 5.5.56 client against a mariadb 10 server and I'm having the next error: ERROR 2003 (HY000): Can't connect to MySQL server on 'server' (10061) Subnet source is allowed in mariadb server and grant is given for 'root'@'source_server', it is allowed both IP and hostname. So not sure if it is config problem or compatibility problem. Someone knows please? Thanks beforehand. P.D.: I can connect using dbeaver from my computer client using mysql binaries (but not sure what mysql client version uses dbeaver). Cheers...

4 5

[Maria-discuss] History Length: Purge-able vs. Not Purge-able metrics
by mariadb＠Biblestuph.com 10 Mar '22

10 Mar '22

Greetings, I know I can get the current undo log history length via: > show status like '%history%'; +----------------------------+-------+ | Variable_name | Value | +----------------------------+-------+ | Innodb_history_list_length | 854 | +----------------------------+-------+ but my understanding is that at any given point in time that number represents both the records that can be purged because they are no longer needed by any current transactions (and the purge threads for whatever reason haven't gotten to them yet), as well as those that cannot be purged yet because there are current transactions running that may still need them. So the question is, is there any way to know the difference between those two? I.E., how many are waiting to be purged and how many cannot yet be purged? And a related question. Will the undo log size (the physical size of the file) grow even when there are many entries in the history that can be purged first? Or are those unneeded records purged first and that space reused before the undo log is made larger? Or perhaps I'm mis-understanding the process? TIA, Dan

1 0