February 2024 - discuss - lists.mariadb.org

External MyISAM partitions
by Jan Křístek 07 Aug '24

07 Aug '24

Hi, We have an old instance of MariaDB 10.3.9/10.3.39, with historical data. Every month I copy an old MyISAM partition (binary files) from the same version of the engine (but a different instance) to a big volume and replace an empty partition in the database with symlinks to the newly copied two files (MYD, MYI - when the engine is stopped). I have been doing it for a year or two, checking each time the data are accessible afterwards. This month it happened, that the data are not accessible anymore, and the database throwing an exception: *Got error 140: "Wrong create options" from storage engine MyISAM.* I tried doing it in a new instance, each time I replace a partition with a link to file elsewhere, the error appeared again. Does anyone have any ideas, why it's showing the error and how to avoid it? I cannot recall changing anything in the database configuration, upgrading any database, or doing any other changes. Thanks for any help you can provide, Jan

4 7

next and previous words
by ChipsRunner 24 Feb '24

24 Feb '24

Hi I've noticed that between debian 10 and 11 (mariadb-client-core-10.3 and mariadb-client-core-10.5) the client console tool (CLI) treats words in a different way: alt+f and alt+b will skip the dot on the new version. Example if I have something like 'test.domain.com' using alt+f on the old version would treat 'test', 'domain' and 'com' as three separate words while the new version would skip at the end of '.com' Is there a way to restore the old behaviour ? Thank you, PM

2 2

Back again for more help
by Ken Wright 21 Feb '24

21 Feb '24

Now that you kind people have pointed me in the right direction as far as log-bin was concerned, I've moved on to trying to replicate the databases from the primary to the secondary. I've created the connection profile and started the secondary connection, but when I ran show slave 'master01' status\G I got the following error: Last_Errno: 1062 Last_Error: Could not execute Write_rows_v1 event on table databasename.oc_filecache; Duplicate entry '110' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log master-bin.00000#, end_log_pos ###### How do I resolve this duplicate entry error? And do I need to do the same resolution on the primary as well? Ubuntu Server 23.10, mariadb version 15.1 Distrib 10.11.6-MariaDB Ken -- If you ever think international affairs make sense, remember this: because a Serb shot an Austrian in Bosnia, Germany invaded Belgium.

3 2

Setting up primary-secondary replication
by Ken Wright 17 Feb '24

17 Feb '24

Greetings! I'm trying to set up a backup email server using Ubuntu 23.10 Server. I want to replicate my MariaDB databases from the primary email server to the secondary, but whenever I add the line log-bin = /var/log/mysql/master-bin to /etc/mysql/mariadb.conf.d/50-server.cnf MariaDB fails to restart. I've looked for help online, but haven't had any luck. Can anyone help? Further details available on request. Ken -- If you ever think international affairs make sense, remember this: because a Serb shot an Austrian in Bosnia, Germany invaded Belgium.

3 4

Windows downloads
by madhon＠madhon.co.uk 16 Feb '24

16 Feb '24

Have the windows downloads for versions 10.6.17 and 10.11.7 been pulled as the only option i see are source and linux ?

3 2

Slow log and processlist.memory_used
by Gordan Bobic 13 Feb '24

13 Feb '24

In processlist, there is a column called memory_used. Is there a way to make the peak value for a query get logged into slow log? Failing that, does the performance_schema provide any such info for previously run statements to go with statement digests? Or is the only place where this can be found in the information_schema.processlist table while the query is running?

1 0

Upgrading MariaDB 10.6.15 to 10.6.17 on Ubuntu 18.04 (unsupported)
by stephan.vos＠metacom.net 11 Feb '24

11 Feb '24

We are currently unable to upgrade our server os from Ubuntu 18.04 to 22.04. So we are stuck on MariaDB 10.6.15 and cannot apply any subsequent minor/major releases. Is it possible to somehow use installation binary package for Focal/Jammy or worse case recompiling from source for 18.04?

4 10

Fwd: REGEXP_REPLACE behaviour
by Richard Ellerbrock 07 Feb '24

07 Feb '24

Hi All, I am trying to understand the behaviour of REGEXP_REPLACE when there is a backslash in the subject string. It appears that the subject needs to have \'s escaped which is not desirable (see example 1 below). I can understand having to escape \'s in the regex, but not the subject string. Any suggestions? Thanks. Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 397751 Server version: 10.11.5-MariaDB MariaDB Server Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> SELECT REGEXP_REPLACE('Et12\4', '^Et', 'Ethernet'); +---------------------------------------------+ | REGEXP_REPLACE('Et12\4', '^Et', 'Ethernet') | +---------------------------------------------+ | Ethernet124 | +---------------------------------------------+ 1 row in set (0.000 sec) MariaDB [(none)]> SELECT REGEXP_REPLACE('Et12\\4', '^Et', 'Ethernet'); +----------------------------------------------+ | REGEXP_REPLACE('Et12\\4', '^Et', 'Ethernet') | +----------------------------------------------+ | Ethernet12\4 | +----------------------------------------------+ 1 row in set (0.000 sec) MariaDB [(none)]> SELECT REGEXP_REPLACE('Et12/4', '^Et', 'Ethernet'); +---------------------------------------------+ | REGEXP_REPLACE('Et12/4', '^Et', 'Ethernet') | +---------------------------------------------+ | Ethernet12/4 | +---------------------------------------------+ 1 row in set (0.000 sec) MariaDB [(none)]> SELECT REGEXP_REPLACE('Et12 4', '^Et', 'Ethernet'); +---------------------------------------------+ | REGEXP_REPLACE('Et12 4', '^Et', 'Ethernet') | +---------------------------------------------+ | Ethernet12 4 | +---------------------------------------------+ 1 row in set (0.000 sec) -- Richard Ellerbrock

2 3

Question regarding AMD EPYC servers and MariaDB
by highclass99 06 Feb '24

06 Feb '24

Hello, In the past when 2nd gen EPYC's were launching and beating Intel servers on most benchmarks, I visited a MariaDB conference and when I asked a senior MariaDB engineer, and asked whether he recommended AMD servers. At that time, he recommended Intel for MariaDB, because MariaDB had much more Intel testing equipment and was optimized for Intel. I am curious whether that is still the case, and whether MariaDB should be more optimized for Intel? For example, would AMD EPYC 7763 vs Intel Platinum 8380, would one be recommended over the other for MariaDB? (of course cores, and workload differ, but on a general perspective) Thank you.

3 3

Replication corrupts index on InnoDB
by Oliver Welter 05 Feb '24

05 Feb '24

Hi All, I have a very strange problem which I am not able to debug any further, so I kindly ask here for any advise to find the root cause of this issue. I run a master-slave replication setup, both servers run on Debian Bookworm with the packages from the distro (10.11.4-MariaDB-1~deb12u1-log). There are two tables in two databases with the same setup (same shop software) and both suffer from recurring index corruption on the slave side. While the master server works without any issues, the slave machine stops replicating from time to time with the error: Last_Errno: 1712 Last_Error: Error 'Index s_order_details is corrupted' on query. Default database: 'foobar_shop'. Query: 'DELETE FROM s_order_details WHERE orderID='40007'' After rebuilding the index by running "alter table foobar_shop.s_order_details engine=innodb" I can restart the slave and it works again. What I did so far: Rebuild the whole slave from fresh SQL Dumps (twice!) Changed replication to "Using_Gtid: Slave_Pos" Reduced slave parallel threads Settings as different from debian defaults binlog_format = mixed expire_logs_days = 1 max_binlog_size = 256M slave_parallel_max_queued=524288 slave_parallel_threads=5 sync_binlog=0 sync_relay_log=0 innodb_flush_log_at_trx_commit=0 best regards Oliver -- Protect your environment - close windows and adopt a penguin!

2 4