- discuss - lists.mariadb.org

can you purge data older than 4 months old
by robert k Wild 29 Jun '23

29 Jun '23

hi all, i was just wondering i know about the "mysqlcheck -a and -o" ie to optimize and to analyse ie to cut it down in size but NOT to purge any data but is there like a purge option to delete all data older than 4 months old in the database thanks, rob -- Regards, Robert K Wild.

2 2

2023 MariaDB (Un)Conference and MariaDB Server Fest
by Ian Gilfillan 29 Jun '23

29 Jun '23

The MariaDB (Un)Conference, for MariaDB Server developers, and the MariaDB Server Fest, for anyone interested in MariaDB Server, will be taking place from 3 - 5 October as hybrid events, both in Helsinki and online. See https://mariadb.org/fest2023/ for details. The CfP for both events is available at https://mariadb.org/fest2023cfp/

1 0

mysql restore error
by robert k Wild 26 Jun '23

26 Jun '23

hi all, i successfully backed up the database /opt/aspera/common/mysql/bin/mysqldump -u root -p'password' aspera_console > /mnt/pixit/engineering/aspera_console/mysql_backups/20230623.sql then i try to restore it, first i delete the database and create the database /opt/aspera/common/mysql/bin/mysql -u root -p'password' drop database aspera_console; create database aspera_console; then run the restore command and i get the error /opt/aspera/common/mysql/bin/mysql -u root -p'password' aspera_console < /mnt/pixit/engineering/aspera_console/mysql_backups/20230623.sql ERROR 1305 (42000) at line 80504: FUNCTION aspera_console.report_user_id does not exist luckily this is not the live vm, its a clone of the live, so im messing around thanks, rob -- Regards, Robert K Wild.

2 4

Very large ibdata1 growth (335Gb) with 10.6.13, solved in 10.6.14 ?
by Simon Avery 20 Jun '23

20 Jun '23

Hi All, We run around 60 Mariadb 10.6 servers on EL in vms and varying workloads. Some time after they updated from 10.6.12 to 10.6.13, four of the busiest started showing higher disk usage than expected. Upon investigation, /var/lib/mysql/ibdata1 was exceptionally large, up to 335Gb, and was still growing at several Gb/day. Note: All servers have only run with "innodb_file_per_table" set and only have innodb engines for user DBs. I cobbled together some data collection just before I went on holiday and checked the graphs today. (Pic attached - if not stripped by the list software) [A picture containing screenshot, line, parallel Description automatically generated] Four machines growing, rest static. Two affected machines stopped growing a week ago - and on checking, Mariadb was upgraded from 10.6.13 to 10.6.14 on them and they were rebooted then. The two still growing are still running 10.6.13 My questions! 1. Am I right that this was a known bug in Mariadb and has been resolved with the .14 release? 2. The .14 release notes mention "InnoDB does not free UNDO after the fix of MDEV-30671 (MDEV-31234)" - is the failure to free UNDO logs a likely cause for ibdata1 to grow, given that it stores the undo log? (The two worst affected machines process many million queries a day) 3. To recover this space, I will need to do a full mysqldump, wipe and reimport of the data, correct? I guess I'm mostly asking for reassurance that this issue is now resolved and that once I schedule in the downtime to recover the space, that it's not going to resurface... Thanks, Simon

2 2

Fwd: DBA in Tokyo
by James Tobin 19 Jun '23

19 Jun '23

Hello, I'm working with an employer that is looking to hire a DBA in Tokyo. Consequently, I had hoped some members of this list may like to discuss. I can be reached using "JamesBTobin (at) Gmail (dot) Com". Kind regards, James

1 0

Connector/C fails to read MariaDB 10.6+ binary logs
by sruli67＠gmail.com 15 Jun '23

15 Jun '23

Hi, I'm using MariaDB Connector/C to 3.3.5 to read binary logs. It works perfectly for MySQL 8.0 and MariaDB 10.5 databases. For MariaDB 10.6 and above, mariadb_rpl_fetch() crashes (!) if the binlog contains XA transactions. Specifically, the function fails when it tries to read event type GTID with this contents: 'XA START X\'54584e31\',X\'\',1 GTID 0-1-21' Please advise Sruli Ganor

4 9

[Maria-discuss] Backup on the replication server getting affected
by ragul rangarajan 09 Jun '23

09 Jun '23

3 3

Re: [Maria-discuss] Restore from mysqldump fails with "Error in foreign key constraint"
by mark f edwards 05 Jun '23

05 Jun '23

How is providers in the `xu6gc_tj_notification_providers' table defined? Is it also varchar(100) character sat uft8mbr collate utf8mb4-general-ci ?? The parent and child columns has to match exactly. On June 3, 2023, at 7:55 AM, Alex <mysqlstudent(a)gmail.com> wrote: Hi, I'm trying to use mysqlbackup to backup a mariadb-10.5.19 database on fedora37 server using the following: # mysqldump --verbose -u root -ppass --result-file=/var/backup/mysql-backup/backup-lsalex-2023-06-03-13008.sql lsalex I usually use a more involved mysqlbackup command, but it also failed, so I figured it would be better to start out more simply as above. It fails with the following when restoring to a new, test database: # mysql -u root -p lstest < /var/backup/mysql-backup/backup-lsalex-2023-06-03-13008.sql Enter password: ERROR 1005 (HY000) at line 12884: Can't create table `lsalex`.`xu6gc_tj_notification_user_exclusions` (errno: 150 "Foreign key constraint is incorrectly formed") This is a backup/restore of a Joomla database. Am I using the wrong command to perform the backup or restore? This isn't a database that I created and I really have no idea how it works. I've also searched extensively for this error, and it appears to be a programming error, not a database error, but obviously I have no control over Joomla programming. Here's what I found from "SHOW ENGINE INNODB STATUS": LATEST FOREIGN KEY ERROR ------------------------ 2023-06-03 10:09:01 0x7f3a8d8516c0 Error in foreign key constraint of table `lstest`.`xu6gc_tj_notification_user_exclusions`: Create table `lstest`.`xu6gc_tj_notification_user_exclusions` with foreign key `xu6gc_tj_notification_user_exclusions_ibfk_1` constraint failed. Field type or character set for column 'provider' does not match referenced column 'provider'.------------ Here's the lines from the backup mentioned in the error message: 12884 CREATE TABLE `xu6gc_tj_notification_user_exclusions` ( 12885 `user_id` int(11) NOT NULL, 12886 `client` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL, 12887 `key` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL, 12888 `provider` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL, 12889 KEY `client1` (`client`,`provider`(50),`key`), 12890 KEY `key` (`key`), 12891 KEY `provider` (`provider`), 12892 CONSTRAINT `xu6gc_tj_notification_user_exclusions_ibfk_1` FOREIGN KEY (`provider`) REFERENCES `xu6gc_tj_notification_providers` (`provider`) 12893 ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci; Any ideas are greatly appreciated.

5 4

[Maria-discuss] Restore from mysqldump fails with "Error in foreign key constraint"
by Alex 03 Jun '23

03 Jun '23

Hi, I'm trying to use mysqlbackup to backup a mariadb-10.5.19 database on fedora37 server using the following: # mysqldump --verbose -u root -ppass --result-file=/var/backup/mysql-backup/backup-lsalex-2023-06-03-13008.sql lsalex I usually use a more involved mysqlbackup command, but it also failed, so I figured it would be better to start out more simply as above. It fails with the following when restoring to a new, test database: # mysql -u root -p lstest < /var/backup/mysql-backup/backup-lsalex-2023-06-03-13008.sql Enter password: ERROR 1005 (HY000) at line 12884: Can't create table `lsalex`.`xu6gc_tj_notification_user_exclusions` (errno: 150 "Foreign key constraint is incorrectly formed") This is a backup/restore of a Joomla database. Am I using the wrong command to perform the backup or restore? This isn't a database that I created and I really have no idea how it works. I've also searched extensively for this error, and it appears to be a programming error, not a database error, but obviously I have no control over Joomla programming. Here's what I found from "SHOW ENGINE INNODB STATUS": LATEST FOREIGN KEY ERROR ------------------------ 2023-06-03 10:09:01 0x7f3a8d8516c0 Error in foreign key constraint of table `lstest`.`xu6gc_tj_notification_user_exclusions`: Create table `lstest`.`xu6gc_tj_notification_user_exclusions` with foreign key `xu6gc_tj_notification_user_exclusions_ibfk_1` constraint failed. Field type or character set for column 'provider' does not match referenced column 'provider'.------------ Here's the lines from the backup mentioned in the error message: 12884 CREATE TABLE `xu6gc_tj_notification_user_exclusions` ( 12885 `user_id` int(11) NOT NULL, 12886 `client` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL, 12887 `key` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL, 12888 `provider` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL, 12889 KEY `client1` (`client`,`provider`(50),`key`), 12890 KEY `key` (`key`), 12891 KEY `provider` (`provider`), 12892 CONSTRAINT `xu6gc_tj_notification_user_exclusions_ibfk_1` FOREIGN KEY (`provider`) REFERENCES `xu6gc_tj_notification_providers` (`provider`) 12893 ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci; Any ideas are greatly appreciated.

1 0

Re: [Maria-discuss] Backup on the replication server getting affected
by andrei.elkin＠pp.inet.fi 02 Jun '23

02 Jun '23

Howdy Ragul, > Hi Andrei, > > Do we have any procedures to reproduce the issue MDEV-30780? Thanks for posting the gdb bt:s. They rule out 30780 yet not suggesting to me enough about the hang reason. This is something new to me and does deserve filing an MDEV ticket. Still I'd defer that until one has confirmed the same issue is seen on the latest 10.6. So you could run your load against the most recent slave version that'd be at least the safest (for our time). It might be (a slave worker) Thread 80 spinning inside #6 0x000055de407a0a3c in log_write_up_to (lsn=<optimized out>, lsn@entry=216757233923297, flush_to_disk=flush_to_disk@entry=false, rotate_key=rotate_key@entry=false, a goto repeat "loop". That hopefully you can confirm any next time the hang appears back. Could you please check whether #6 calls iteratively indeed `group_commit_lock::release()`? (With e.g (gdb) br thd_decrement_pending_ops thread 80 of course the number may change:-)). All the other slave worker threads may be waiting for the 80 but I can't confirm that until more data gets available. Namely I need to see the output of (gdb) thr app all get_about_worker_thread where the latter is defined as define get_about_worker_thread if $_any_caller_is ("handle_rpl_parallel_thread", 50) bt p handle_rpl_parallel_thread::rpt if (handle_rpl_parallel_thread::rpt->thd->rgi_slave) p handle_rpl_parallel_thread::rpt->thd->rgi_slave p handle_rpl_parallel_thread::rpt->thd->rgi_slave->current_gtid p handle_rpl_parallel_thread::rpt->thd->rgi_slave->gtid_sub_id p handle_rpl_parallel_thread::rpt->thd->rgi_slave->worker_error end end end > Unable to reproduce the issue locally but it occurs at random. to require some more patience from us. I belive we can resolve it while you're helping so generously! Cheers, Andrei > > Regards, > Ragul > > On Mon, May 29, 2023 at 7:06 PM ragul rangarajan <ragulrangarajan(a)gmail.com> wrote: > > Thanks Andrei, > > Hope my issue is more related to the issue MDEV-30780 optimistic parallel slave hangs after hit an error > Trying to reproduce with a minimal database.

1 0