- discuss - lists.mariadb.org

[Maria-discuss] Understanding SQL queries
by João Paulo Almeida 14 Apr '22

14 Apr '22

Dear MariaDB Users, We are currently carrying out some research on the understanding and usability of different relational schemas (as part of a Ph.D. student's thesis work). We would like to invite you to contribute to this research by answering a small number of questions on SQL query interpretation. Participation is via an anonymous form and there are only 7 questions, so it should not take more than 10 minutes of your time: https://forms.gle/EA2jYGf4CTmLfEiaA We thank you in advance and would appreciate it if you could also share this research with colleagues who also have a background on SQL. thank you, João Paulo A. Almeida Federal University of Espírito Santo

2 1

[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

[Maria-discuss] Unable to find specific format for mariaDB 10.6.*
by ragul rangarajan 25 Feb '22

25 Feb '22

Hi Team, I try to get MariaDB 10.6.* *bintar-linux-x86_64 tar* from http://archive.mariadb.org/ But I couldn't find any other formats except *bintar-linux-systemd-x86_64 *as in the older version. Can someone please share where to get* bintar-linux-x86-64 *for 10.6.* MariaDB version as like below for 10.5.* https://archive.mariadb.org/mariadb-10.5.15/bintar-linux-x86_64/mariadb-10.… Thanks and regards, Ragul

3 4

[Maria-discuss] demo: running MariaDB with rootless Podman and socket activation
by Erik Sjölund 17 Feb '22

17 Feb '22

Hi, Support for socket activation was added to MariaDB in release 10.6 (released April 2021). Podman also supports socket activation so I thought it would be interesting to combine both of them into a systemd user service. I wrote a small demo: https://github.com/eriksjolund/mariadb-podman-socket-activation (tweet: https://twitter.com/eriksjolundcomp/status/1491162016429768704) and got it to work. Do you have any suggestions on how to improve this? Thanks, Erik Sjölund

2 3

[Maria-discuss] Fwd: [MariaDB Announce] MariaDB 10.8.1 RC and MariaDB 10.7.2, 10.6.6, 10.5.14, 10.4.23, 10.3.33 and 10.2.42 now available
by Reindl Harald 10 Feb '22

10 Feb '22

https://downloads.mariadb.org/mariadb/10.3.33/ points to a form with 10.6 preselected because a redirect to https://mariadb.org/download/?t=mariadb&p=mariadb&r=10.6.5&os=Linux&cpu=x86… and in that useless form 10.3.32 is the newest you can select when trying to download sources is there a reason why such nonsense on download pages is developed other than "some people need to be busy"? when you change to 10.3 and have selcted "source" before the form goes back to Linux with systemd as selection head - table - match -------- Weitergeleitete Nachricht -------- Betreff: [MariaDB Announce] MariaDB 10.8.1 RC and MariaDB 10.7.2, 10.6.6, 10.5.14, 10.4.23, 10.3.33 and 10.2.42 now available MariaDB 10.3.33 - Release Notes: https://mariadb.com/kb/en/mdb-10333-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10333-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.3.33/

2 1

[Maria-discuss] Weird behavior in Fedora 34 server
by Miguel Lavalle 05 Jan '22

05 Jan '22

Hi, I am installing MariaDB in Fedora 34 server with the following sequence of commands: sudo dnf upgrade -y sudo dnf install -y mariadb-server mariadb-devel sudo dnf -y install git vim With this sequence of commands, I get the following installed: $ mysql --version mysql Ver 15.1 Distrib 10.5.13-MariaDB, for Linux (x86_64) using EditLine wrapper and I can successfully perform the initial setup of the root password: sudo mysqladmin -u root password password and continue with the rest of my installation. However, if I change the sequence of commands to: sudo dnf upgrade -y sudo dnf -y install git vim sudo dnf install -y mariadb-server mariadb-devel What I get installed instead is: $ mysql --version mysql Ver 8.0.27 for Linux on x86_64 (Source distribution) and the 'sudo mysqladmin -u root password password' command fails with: mysqladmin: unable to change password; error: 'You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '() IDENTIFIED BY 'secretdatabase'' at line 1' Could anyone shed some light on this? Thanks!

3 8

[Maria-discuss] Incremental backup with mariabackup and run-mariabackup
by Dave Wreski 02 Jan '22

02 Jan '22

Hi, I'm using mariadb-10.5.13 on fedora34 with run-mariabackup from https://github.com/omegazeng/run-mariabackup. Has anyone used this backup script or have any recommendations for ones that help to automate the process of using mariabackup for backups? This script appears to create an infinite amount of incremental backups once the original full backup is created. I believe this makes it necessary to restore each of the incrementals on top of the base. If the backups are stored off-site, this creates magnitudes more data that's needed to restore, and increases the time to restore it. It also only appears possible to backup the entire system, not just individual databases. Do you have any recommendations for other scripts that ease the process of making and restoring backups? Thanks, Dave

1 0

[Maria-discuss] sys schema backup
by William Edwards 04 Dec '21

04 Dec '21

Hi, The 'sys' schema is documented to be "A collection of views, functions and procedures to help MySQL administrators get insight in to MySQL Database usage." Is there anything in this schema that should be backed up, or can I skip it when creating backups? -- With kind regards, William Edwards

3 2

[Maria-discuss] [Warning] WSREP: certification interval for trx source [...] exceeds the limit of 16384
by Giovanni Agozzino 01 Dec '21

01 Dec '21

Hi people, I'm relatively new to Mariadb+Galera and I'm trying to understand how to manage when a node goes down the best way. I don’t know if this is the right place to ask. If not, I’d appreciate suggestions for where to ask. I am using 1:10.6.5+maria~hirsute galera-4 26.4.9-hirsute I would understand what is the meaning of the warning: [Warning] WSREP: certification interval for trx source [...] exceeds the limit of 16384 and what are the ways to avoid it. I'll explain when I encounter it: I shut down one of my three mariadb nodes during peak hours and I wait to restart it until a SST is triggered. The SST is succesfully done (both the donor and the joiner go without errors). But when applying the IST post SST to keep up with the latest transactions, I see these warning in both donor (before switching from donor/desynced to synced state) and joiner (after completing SST). What is the implication of this warning? I suppose is not the certification failing or I would have errors, but I don't know if is serious business or not. And there is a parameter to tune in the way to avoid this warning? Thank you very much. Best regards, Giovanni

1 0