July 2023 - discuss - lists.mariadb.org

[Maria-discuss] Galera 23.2.7 mariadb 5.5.33a msvc 1600 binaries available
by Yann Nayn 05 Dec '24

05 Dec '24

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.

3 2

Query on Building Maria DB for different Compression Algorithm
by Raj, Rahul 10 Aug '23

10 Aug '23

[AMD Official Use Only - General] Hi, I am building MariaDB from source code and have queries on linking of compression algorithm. Before building the source code of MariaDB, I am exporting the path for SNAPPY or LZMA or the algorithm which is currently it supports. Then I build the code with - cmake -B . -DCMAKE_INSTALL_PREFIX=$PWD/maria_bin -DPLUGIN_MROONGA=NO -DPLUGIN_ROCKSDB=NO cmake --build . -j cmake -install . It compiled the code and installed in the specified location. When I checked the lib/plugin folder it has generated, provider_lzma.so or provider_snappy.so files and when I did ldd on that .so file, it has given the path from where it is fetching the liblzma.so.1 or libsnappy.so.1 file. Query: 1. The path which ldd shows for provider_lzma.so or provider_snappy.so is taking form default path, and it is not from the path which I am exporting the library and bin path - could you please explain me the correct steps. 2. Is there any way or any Flag we can set to switch between different compression method during build time itself, and in which log we can check it has linked properly. 3. How to benchmark the linked compression method and how we can see it is using the linked compression method from the custom path of .so files. Kindly help on above query. Thanks Rahul Raj

4 9

Expected release date MariaDB 10.6.15
by William Edwards 01 Aug '23

01 Aug '23

Hi, Is MariaDB 10.6.15 expected to be released this week? According to Jira[1], it is 4 days overdue. This version will include a fix that I'm waiting for. Met vriendelijke groeten, William Edwards [1]: https://jira.mariadb.org/projects/MDEV/versions/29013

3 4

Help us redesign the mariadb.org website
by Ian Gilfillan 18 Jul '23

18 Jul '23

We are currently re-designing the mariadb.org website and you are invited to participate in this process. The interactive study shouldn't take longer than 10 to 15 minutes to complete and will close at midnight on Thursday 20 July 2023 (UTC-8). Access the study here: (no registration or login is required) https://study.uxtweak.com/cardsort/gkeYA0HPSXawp6YNsjllU The activity involves a method called Card Sorting, which will influence how we design the information architecture of the website: its structure, navigation and the findability of content and functionality. Your inclusion in this effort is important and will help to inform and assist us in designing an intuitive, usable and effective future website. Many thanks from the website redesign team MariaDB Foundation

1 0

Advice on Replication
by Andrew Gable 13 Jul '23

13 Jul '23

5 4

Re: Sandboxing mariabackup
by Tom Worster 07 Jul '23

07 Jul '23

Hi Daniel, That part is looking good for now but I gotta do fire drills validate the whole shebang. There's something almost blog worthy about this. mysqldump started as a handy import export utility and ended up being an exquisite point-in-time logical SQL snapshot tool. Now xtrabackup and mariabackup are so astonishingly fast at restoration/recovery they can't be ignored. But they are terrifying! They operate directly on the datadir. mysqldump is a nice friendly SQL client like any other. Does that make sense? An SQL client can ruin the DB as well as anything else if it has the right permissions (pun!). Hence subtracting permission to write datadir from the mariabackup process feels like a step to parity. Tom On 7/6/2023 6:52:17 PM, "Daniel Black" <daniel(a)mariadb.org> wrote: >Glad you worked it out. > >I did mean to write this onlist a while ago. Got saved a draft message >and I forgot about it. > >On Thu, Jul 6, 2023 at 10:47 PM Tom Worster <fsb(a)thefsb.org> wrote: >> >> On 7/6/2023 7:14:50 AM, "Daniel Black" <daniel(a)mariadb.org> wrote: >> >> >> I prefer to sandbox systemd services with ProtectSystem=strict. >> >> Especially so when User=root. >> > >> >Should be able to use User=mysql (or whatever the mariadb.service is >> >running as), provided the backup directory is also mysql: owned. >> > >> Thanks Daniel. >> >> Yes. I discovered that in subsequent testing. >> spin >> And I found that only target-dir and tmpdir need to be read-write. I >> forget what made me think that wasn't enough. >> >> To run as mariabackup as mysql user but with read-only access to datadir >> I separated the mariabackup part of the overall hourly backup script >> into its own service unit: >> [Unit] >> Description=mariabackup DBs >> OnFailure=unit-status-mail(a)%n.service unit-status-pushover(a)%n.service >> [Service] >> User=mysql >> Type=oneshot >> ProtectSystem=strict >> ReadWritePaths=/pool2/mariabackup /pool2/mariabackup_tmpdir >> ExecStart=/path/to/backup_maria.sh >> >> This is /path/to/backup_maria.sh. It's on a replica and the test of prev >> and new size are a check (among others) that the replica isn't stuck. >> #!/bin/bash >> prev_backup_size=`du -s /pool2/mariabackup` >> rm -rf /pool2/mariabackup/* >> mariabackup --backup --target-dir=/pool2/mariabackup/ >> --tmpdir=/pool2/mariabackup_tmpdir --user=mariabackup --password=__ >> mariabackup --prepare --target-dir=/pool2/mariabackup/ >> --tmpdir=/pool2/mariabackup_tmpdir >> new_backup_size=`du -s /pool2/mariabackup` >> if [ "$prev_backup_size" = "$new_backup_size" ] >> then >> echo WARNING: Consecutive mariabackup sizes unchanged >> # FIXME send alerts >> fi >>

2 2

Sandboxing mariabackup
by Tom Worster 06 Jul '23

06 Jul '23

I prefer to sandbox systemd services with ProtectSystem=strict. Especially so when User=root. So when ProtectSystem=strict, which dirs need to be ReadWritePaths to run `mariabackup --backup` and `mariabackup --prepare`? So far I got the --target-dir and the --tmpdir. Is that sufficient? tia Tom

2 2

stop database before truncate
by robert k Wild 03 Jul '23

03 Jul '23

hi all, looking at this guide https://www.ibm.com/support/pages/temporarily-reduce-space-taken-console-da… do i ideally have to stop the database before i truncate some tables ie /opt/aspera/common/mysql/bin/mysql -u root -p'password' aspera_console TRUNCATE* fasp_sessions fasp_files fasp_rates * *jobs job_steps* *thanks,* *rob* -- Regards, Robert K Wild.

2 5