- discuss - lists.mariadb.org

[Maria-discuss] subscribe
by Ruben Safir 29 Jan '23

29 Jan '23

subscribe -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

1 0

[Maria-discuss] Query got stuck while we fetch for specific timestamp
by ragul rangarajan 27 Jan '23

27 Jan '23

Hi all, I have a TableA with data around 1.4Billion which was partitioned by timestamp. <https://stackoverflow.com/posts/75231474/timeline> TableA ( Column1, Column 2....Column N, timestamp) Partition by times I was able to see a weird behavior recently on this table where querying specific timestamps ended in an issue (Query getting stuck more than expected time - 10min and block IO utilization which inturn lead to service degradation). 127.0.0.1:3307>select * from TableA where cloumn1=v1 and cloumn2=v2 and cloumn3=v3 and cloumn4=v4 and cloumn5=v5 and (timestamp between 1673319600 and 1673319600);^CCtrl-C -- query killed. Continuing normally. ERROR 1317 (70009): Query execution was interrupted 127.0.0.1:3307> analyze select * from TableA where cloumn1=v1 and cloumn2=v2 and cloumn3=v3 and cloumn4=v4 and cloumn5=v5 and (timestamp between 1673319600 and 1673319600);^CCtrl-C -- query killed. Continuing normally. ERROR 1317 (70100): Query execution was interrupted 127.0.0.1:3307> explain select * from TableA where cloumn1=v1 and cloumn2=v2 and cloumn3=v3 and cloumn4=v4 and cloumn5=v5 and (timestamp between 1673319600 and 1673319600); +------+-------------+--------------+------+---------------+------+---------+------+------+-------------+| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |+------+-------------+--------------+------+---------------+------+---------+------+------+-------------+| 1 | SIMPLE | TableA | ALL | PRIMARY | NULL | NULL | NULL | 14 | Using where |+------+-------------+--------------+------+---------------+------+---------+------+------+-------------+1 row in set (0.042 sec) while the same was working under different timestamp 127.0.0.1:3307> explain select * from TableA where cloumn1=v1 and cloumn2=v2 and cloumn3=v3 and cloumn4=v4 and cloumn5=v5 and (timestamp between 1673319600+3600 and 1673319600+7200+7200+7200+7200+7200+7200);+------+-------------+--------------+------+---------------+---------+---------+-------------------------------+------+-------------+| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |+------+-------------+--------------+------+---------------+---------+---------+-------------------------------+------+-------------+| 1 | SIMPLE | TableA | ref | PRIMARY | PRIMARY | 7 | const,const,const,const,const | 12 | Using where |+------+-------------+--------------+------+---------------+---------+---------+-------------------------------+------+-------------+1 row in set (0.002 sec) 127.0.0.1:3307> analyze select * from TableA where cloumn1=v1 and cloumn2=v2 and cloumn3=v3 and cloumn4=v4 and cloumn5=v5 and (timestamp between 1673319600+3600 and 1673319600+7200+7200+7200+7200+7200+7200);+------+-------------+--------------+------+---------------+---------+---------+-------------------------------+------+--------+----------+------------+-------------+| id | select_type | table | type | possible_keys | key | key_len | ref | rows | r_rows | filtered | r_filtered | Extra |+------+-------------+--------------+------+---------------+---------+---------+-------------------------------+------+--------+----------+------------+-------------+| 1 | SIMPLE | TableA | ref | PRIMARY | PRIMARY | 7 | const,const,const,const,const | 12 | 600.00 | 100.00 | 91.67 | Using where |+------+-------------+--------------+------+---------------+---------+---------+-------------------------------+------+--------+----------+------------+-------------+1 row in set (0.003 sec) Suspecting something might get corrupted in the DB entry for a specific time but not sure how to verify it. 1. Is there any way to check the Data corruption issue in the specific table? a. Tried to check via mysqlcheck but it consumes more time and IO utilization. b. Do we have any other option to check the same in a better way? 1. If we have a problem with DB table entries do we have options to solve this a. Either restarting the active DB or other ways to repair the data to solve the issue like mysqlcheck repair. 1. Not sure why we see NULL in key, Key_len, and possible_key for the first explain statement for the same table. Regards, Ragul R

2 1

[Maria-discuss] [newbie] Include latest ID into INSERT?
by Gilles 23 Jan '23

23 Jan '23

Hello, I need to write a script in SQL to import topics + posts into a phpBB forum. The issue I have is: How can I reference the last topic ID when adding a post to it, since a post must reference a topic? ============ #Create new topic (ie. discussion thread) INSERT INTO `phpbb_topics` (forum_id,topic_title,topic_poster,topic_time) VALUES (); #Add first post to topic #INSERT INTO `phpbb_posts` (topic_id,forum_id,poster_id,post_time,post_username,post_text) VALUES (); INSERT INTO `phpbb_posts` (SELECT LAST_INSERT_ID(),forum_id,poster_id,post_time,post_username,post_text) VALUES (); ============ Can it be done in SQL, or should I write it in eg. Python? Thank you.

1 0

[Maria-discuss] Inspect SQL sentencies in aria_log files
by woodyst 22 Jan '23

22 Jan '23

Hello! Please, forgive me if I am asking in the wrong list so I do not know if it is the correct place for asking this question. I was using MyISAM engine in the past, and I used binlog files for inspecting sql queries executed in the system for debuging purposes. Now I use Aria and I would need to list queries as I did with mysqlbinlog, but for the aria_log files. I have been reading a lot of documentation but I only find that the aria_read_log utility with the display-only option does not print the sql queries as mysqldump did. Please, can anybody help me with this? Thanks in advance. -- Edu.

2 1

[Maria-discuss] Re-starting mariadb again
by Jogchum Reitsma 19 Jan '23

19 Jan '23

Hi, 12th of October I started the topic" Maria-db refuses to start". With the help offered in the conversation following I could access my data by manually starting an older version of Mariadb. I then dumped my tables with mysqldump, one by one, successfully. I also dumped the mysql table. Final advice was to purge all reminiscences of the older versions, and make a fresh start by installing the version of my OS (OpenSuse Tumbleweed). In that new environment, import the dumped data. A few questions remain: - should I, after the install process of the OS version (at the moment 10.10.2-1.1) take further actions to get a fully functioning system? - should I import the dumped "mysql" table? - if yes, should I do that before or after importing the user data? Or doesn't that matter? Again, thanks for your answers! kind regards, Jogchum

1 1

[Maria-discuss] MySQLTuner-perl 2.0.10 with MariaDB 10.3.35 + Plesk
by Dragos Pacher 18 Jan '23

18 Jan '23

Hello, I am looking for an expert opinion on MySQLTuner-perl recommendations and usefulness in my specific case of MariaDB 10.3.35 with Plesk Web Host Edition 18.0.49 Update #2 - with a somehow default installation: one demo site added + some popular components in default state idling - on Rocky Linux 8.7 kernel 4.18.0-425.10.1.el8_7.x86_64. What are your opinions on the recommendations below? My machine is a VirtualBox 7.0.4 one(on Windows 11 22H2 build 22621.1105) with slower Seagate Barracuda PRO disks (non RAID), 8 GB RAM, processor Ryzen 7 3700x(all cores assigned). This was meant just for testing but I am trying to extrapolate some of the results here for a production environment with generous hardware(over 48 GB RAM and newer generation CPUs, NVME/RAIDs). The only way (as of now) for Plesk to work is by coexisting on the same machine with the database server - please take this into consideration. Please see the results below after ~15-24h of Plesk idling on the machine. Also please let me know if you need more data from my side or if I should enable something and rerun a specific test, I can provide detailed statistics if needed. I am really looking forward on how to make this database a bit faster if possible(without enabling really dangerous options). Thank you. [root@pensive-aryabhata ~]# cat /etc/my.cnf # # This group is read both both by the client and the server # use it for options that affect everything # [client-server] # # include all files from the config directory # !includedir /etc/my.cnf.d [mysqld] sql_mode=ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION bind-address = ::ffff:127.0.0.1 local-infile=0 join_buffer_size = 5M # I changed this from 3 to 5 24h before running the MySQLTuner [root@pensive-aryabhata ~]# sysctl -a | grep swapp vm.force_cgroup_v2_swappiness = 0 vm.swappiness = 5 [root@pensive-aryabhata ~]# perl mysqltuner.pl --host 127.0.0.1 >> MySQLTuner 2.0.10 * Jean-Marie Renouard <jmrenouard(a)gmail.com> * Major Hayden <major(a)mhtx.net> >> Bug reports, feature requests, and downloads at http://mysqltuner.pl/ >> Run with '--help' for additional options and output filtering [--] Skipped version check for MySQLTuner script [--] Performing tests on 127.0.0.1:3306 [OK] Currently running supported MySQL version 10.3.35-MariaDB [OK] Operating on 64-bit architecture -------- Log file Recommendations ------------------------------------------------------------------ [OK] Log file /var/log/mariadb/mariadb.log exists [--] Log file: /var/log/mariadb/mariadb.log (13K) [OK] Log file /var/log/mariadb/mariadb.log is not empty [OK] Log file /var/log/mariadb/mariadb.log is smaller than 32 Mb [OK] Log file /var/log/mariadb/mariadb.log is readable. [!!] /var/log/mariadb/mariadb.log contains 15 warning(s). [!!] /var/log/mariadb/mariadb.log contains 2 error(s). [--] 5 start(s) detected in /var/log/mariadb/mariadb.log [--] 1) 2023-01-17 23:36:33 0 [Note] /usr/libexec/mysqld: ready for connections. [--] 2) 2023-01-17 23:36:20 0 [Note] /usr/libexec/mysqld: ready for connections. [--] 3) 2023-01-17 23:23:33 0 [Note] /usr/libexec/mysqld: ready for connections. [--] 4) 2023-01-17 18:18:58 0 [Note] /usr/libexec/mysqld: ready for connections. [--] 5) 2023-01-17 18:18:24 0 [Note] /usr/libexec/mysqld: ready for connections. [--] 4 shutdown(s) detected in /var/log/mariadb/mariadb.log [--] 1) 2023-01-17 23:36:29 0 [Note] /usr/libexec/mysqld: Shutdown complete [--] 2) 2023-01-17 23:36:16 0 [Note] /usr/libexec/mysqld: Shutdown complete [--] 3) 2023-01-17 23:20:59 0 [Note] /usr/libexec/mysqld: Shutdown complete [--] 4) 2023-01-17 18:18:50 0 [Note] /usr/libexec/mysqld: Shutdown complete -------- Storage Engine Statistics ----------------------------------------------------------------- [--] Status: +ARCHIVE +Aria +BLACKHOLE +CSV +FEDERATED +InnoDB +MEMORY +MRG_MyISAM +MyISAM +PERFORMANCE_SCHEMA +SEQUENCE [--] Data in InnoDB tables: 8.2M (Tables: 267) [OK] Total fragmented tables: 0 -------- Analysis Performance Metrics -------------------------------------------------------------- [--] innodb_stats_on_metadata: OFF [OK] No stat updates during querying INFORMATION_SCHEMA. -------- Views Metrics ----------------------------------------------------------------------------- -------- Triggers Metrics -------------------------------------------------------------------------- -------- Routines Metrics -------------------------------------------------------------------------- -------- Security Recommendations ------------------------------------------------------------------ [OK] There are no anonymous accounts for any database users [OK] All database users have passwords assigned [!!] There is no basic password file list! -------- CVE Security Recommendations -------------------------------------------------------------- [--] Skipped due to --cvefile option undefined -------- Performance Metrics ----------------------------------------------------------------------- [--] Up for: 13h 39m 22s (45K q [0.920 qps], 1K conn, TX: 38M, RX: 3M) [--] Reads / Writes: 86% / 14% [--] Binary logging is disabled [--] Physical Memory : 7.6G [--] Max MySQL memory : 3.9G [--] Other process memory: 0B [--] Total buffers: 417.0M global + 23.7M per thread (151 max threads) [--] Performance_schema Max memory usage: 0B [--] Galera GCache Max memory usage: 0B [OK] Maximum reached memory usage: 724.6M (9.33% of installed RAM) [OK] Maximum possible memory usage: 3.9G (51.40% of installed RAM) [OK] Overall possible memory usage with other process is compatible with memory available [OK] Slow queries: 0% (0/45K) [OK] Highest usage of available connections: 8% (13/151) [OK] Aborted connections: 0.30% (3/1012) [!!] Name resolution is active: a reverse name resolution is made for each new connection which can reduce performance [OK] Query cache is disabled by default due to mutex contention on multiprocessor machines. [OK] Sorts requiring temporary tables: 0% (0 temp sorts / 306 sorts) [!!] Joins performed without indexes: 228 [!!] Temporary tables created on disk: 90% (8K on disk / 9K total) [OK] Thread cache hit rate: 86% (140 created / 1K connections) [OK] Table cache hit rate: 98% (42K hits / 43K requests) [!!] table_definition_cache (400) is less than number of tables (428) [OK] Open file limit used: 0% (84/32K) [OK] Table locks acquired immediately: 100% (48 immediate / 48 locks) -------- Performance schema ------------------------------------------------------------------------ [!!] Performance_schema should be activated. [--] Sys schema is not installed. -------- ThreadPool Metrics ------------------------------------------------------------------------ [--] ThreadPool stat is disabled. -------- MyISAM Metrics ---------------------------------------------------------------------------- [!!] Key buffer used: 18.3% (23.4M used / 128.0M cache) [OK] Key buffer size / total MyISAM indexes: 128.0M/123.0K [!!] Read Key buffer hit rate: 73.3% (75 cached / 20 reads) -------- InnoDB Metrics ---------------------------------------------------------------------------- [--] InnoDB is enabled. [--] InnoDB Thread Concurrency: 0 [OK] InnoDB File per table is activated [OK] InnoDB buffer pool / data size: 128.0M / 8.2M [!!] Ratio InnoDB log file size / InnoDB Buffer pool size (75%): 48.0M * 2 / 128.0M should be equal to 25% [OK] InnoDB buffer pool instances: 1 [--] Number of InnoDB Buffer Pool Chunk: 1 for 1 Buffer Pool Instance(s) [OK] Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size & Innodb_buffer_pool_instances [OK] InnoDB Read buffer efficiency: 99.08% (182560 hits / 184256 total) [!!] InnoDB Write Log efficiency: 11.48% (114 hits / 993 total) [OK] InnoDB log waits: 0.00% (0 waits / 1107 writes) -------- Aria Metrics ------------------------------------------------------------------------------ [--] Aria Storage Engine is enabled. [OK] Aria pagecache size / total Aria indexes: 128.0M/0B [!!] Aria pagecache hit rate: 91.0% (95K cached / 8K reads) -------- TokuDB Metrics ---------------------------------------------------------------------------- [--] TokuDB is disabled. -------- XtraDB Metrics ---------------------------------------------------------------------------- [--] XtraDB is disabled. -------- Galera Metrics ---------------------------------------------------------------------------- [--] Galera is disabled. -------- Replication Metrics ----------------------------------------------------------------------- [--] Galera Synchronous replication: NO [--] No replication slave(s) for this server. [--] Binlog format: MIXED [--] XA support enabled: ON [--] Semi synchronous replication Master: OFF [--] Semi synchronous replication Slave: OFF [--] This is a standalone server -------- Recommendations --------------------------------------------------------------------------- General recommendations: Check warning line(s) in /var/log/mariadb/mariadb.log file Check error line(s) in /var/log/mariadb/mariadb.log file MySQL was started within the last 24 hours: recommendations may be inaccurate Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1 We will suggest raising the 'join_buffer_size' until JOINs not using indexes are found. See https://dev.mysql.com/doc/internals/en/join-buffer-size.html (specially the conclusions at the bottom of the page). When making adjustments, make tmp_table_size/max_heap_table_size equal Reduce your SELECT DISTINCT queries which have no LIMIT clause Performance schema should be activated for better diagnostics Consider installing Sys schema from https://github.com/mysql/mysql-sys for MySQL Before changing innodb_log_file_size and/or innodb_log_files_in_group read this: https://bit.ly/2TcGgtU Variables to adjust: skip-name-resolve=1 join_buffer_size (> 5.0M, or always use indexes with JOINs) tmp_table_size (> 16M) max_heap_table_size (> 16M) table_definition_cache (400) > 428 or -1 (autosizing if supported) performance_schema=ON key_buffer_size (~ 24M) innodb_log_file_size should be (=16M) if possible, so InnoDB total log files size equals 25% of buffer pool size. # end of MySQL Tuner-perl script #1 # more details [root@pensive-aryabhata ~]# perl mysqltuner.pl --buffers --dbstat --idxstat --sysstat --pfstat --tbstat # # skipped part as the output was too big # -------- Views Metrics ----------------------------------------------------------------------------- -------- Triggers Metrics -------------------------------------------------------------------------- -------- Routines Metrics -------------------------------------------------------------------------- -------- Security Recommendations ------------------------------------------------------------------ [OK] There are no anonymous accounts for any database users [OK] All database users have passwords assigned [!!] There is no basic password file list! -------- CVE Security Recommendations -------------------------------------------------------------- [--] Skipped due to --cvefile option undefined -------- Performance Metrics ----------------------------------------------------------------------- [--] Up for: 13m 5s (3K q [4.741 qps], 1K conn, TX: 1M, RX: 549K) [--] Reads / Writes: 97% / 3% [--] Binary logging is disabled [--] Physical Memory : 7.6G [--] Max MySQL memory : 3.9G [--] Other process memory: 1.1G [--] Total buffers: 417.0M global + 23.7M per thread (151 max threads) [--] Performance_schema Max memory usage: 0B [--] Galera GCache Max memory usage: 0B [--] Global Buffers [--] +-- Key Buffer: 128.0M [--] +-- Max Tmp Table: 16.0M [--] Query Cache Buffers [--] +-- Query Cache: OFF - DISABLED [--] +-- Query Cache Size: 1.0M [--] Per Thread Buffers [--] +-- Read Buffer: 128.0K [--] +-- Read RND Buffer: 256.0K [--] +-- Sort Buffer: 2.0M [--] +-- Thread stack: 292.0K [--] +-- Join Buffer: 5.0M [OK] Maximum reached memory usage: 535.3M (6.90% of installed RAM) [OK] Maximum possible memory usage: 3.9G (51.40% of installed RAM) [OK] Overall possible memory usage with other process is compatible with memory available [OK] Slow queries: 0% (0/3K) [OK] Highest usage of available connections: 3% (5/151) [OK] Aborted connections: 0.00% (0/1594) [!!] Name resolution is active: a reverse name resolution is made for each new connection which can reduce performance [OK] Query cache is disabled by default due to mutex contention on multiprocessor machines. [OK] Sorts requiring temporary tables: 0% (0 temp sorts / 93 sorts) [!!] Joins performed without indexes: 4 [!!] Temporary tables created on disk: 73% (1K on disk / 1K total) [OK] Thread cache hit rate: 99% (5 created / 1K connections) [OK] Table cache hit rate: 89% (3K hits / 3K requests) [!!] table_definition_cache (400) is less than number of tables (428) [OK] Open file limit used: 0% (59/32K) [OK] Table locks acquired immediately: 100% (18 immediate / 18 locks) -------- Performance schema ------------------------------------------------------------------------ [!!] Performance_schema should be activated. [--] Sys schema is not installed. -------- ThreadPool Metrics ------------------------------------------------------------------------ [--] ThreadPool stat is disabled. -------- MyISAM Metrics ---------------------------------------------------------------------------- [!!] Key buffer used: 18.2% (23.3M used / 128.0M cache) [OK] Key buffer size / total MyISAM indexes: 128.0M/123.0K -------- InnoDB Metrics ---------------------------------------------------------------------------- [--] InnoDB is enabled. [--] InnoDB Buffers [--] +-- InnoDB Buffer Pool: 128.0M [--] +-- InnoDB Buffer Pool Instances: 1 [--] +-- InnoDB Buffer Pool Chunk Size: 128.0M [--] +-- InnoDB Log File Size: 48.0M [--] +-- InnoDB Log File In Group: 2 [--] +-- InnoDB Total Log File Size: 96.0M(75 % of buffer pool) [--] +-- InnoDB Log Buffer: 16.0M [--] +-- InnoDB Log Buffer Free: 6.2K [--] +-- InnoDB Log Buffer Used: 8.0K [--] InnoDB Thread Concurrency: 0 [OK] InnoDB File per table is activated [OK] InnoDB buffer pool / data size: 128.0M / 8.2M [!!] Ratio InnoDB log file size / InnoDB Buffer pool size (75%): 48.0M * 2 / 128.0M should be equal to 25% [OK] InnoDB buffer pool instances: 1 [--] Number of InnoDB Buffer Pool Chunk: 1 for 1 Buffer Pool Instance(s) [OK] Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size & Innodb_buffer_pool_instances [!!] InnoDB Read buffer efficiency: 83.63% (8790 hits / 10511 total) [!!] InnoDB Write Log efficiency: 154.55% (17 hits / 11 total) [OK] InnoDB log waits: 0.00% (0 waits / 28 writes) -------- Aria Metrics ------------------------------------------------------------------------------ [--] Aria Storage Engine is enabled. [OK] Aria pagecache size / total Aria indexes: 128.0M/0B [OK] Aria pagecache hit rate: 95.4% (29K cached / 1K reads) -------- TokuDB Metrics ---------------------------------------------------------------------------- [--] TokuDB is disabled. -------- XtraDB Metrics ---------------------------------------------------------------------------- [--] XtraDB is disabled. -------- Galera Metrics ---------------------------------------------------------------------------- [--] Galera is disabled. -------- Replication Metrics ----------------------------------------------------------------------- [--] Galera Synchronous replication: NO [--] No replication slave(s) for this server. [--] Binlog format: MIXED [--] XA support enabled: ON [--] Semi synchronous replication Master: OFF [--] Semi synchronous replication Slave: OFF [--] This is a standalone server -------- Recommendations --------------------------------------------------------------------------- General recommendations: Consider stopping or dedicate server for additional process other than mysqld. Check warning line(s) in /var/log/mariadb/mariadb.log file Check error line(s) in /var/log/mariadb/mariadb.log file Limit charset for column to one charset if possible for psa database. Limit collations for column to one collation if possible for psa database. Limit collations for column to one collation if possible for phpmyadmin database. Check all table collations are identical for all tables in roundcubemail database. Limit collations for column to one collation if possible for roundcubemail database. Limit charset for column to one charset if possible for apsc database. Limit collations for column to one collation if possible for apsc database. Add at least a primary key on table psa.SchemaVersions Add at least a primary key on table psa.suspend_handler_history Add at least a primary key on table psa.WebsitesDiagnosticDomains MySQL was started within the last 24 hours: recommendations may be inaccurate Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1 We will suggest raising the 'join_buffer_size' until JOINs not using indexes are found. See https://dev.mysql.com/doc/internals/en/join-buffer-size.html (specially the conclusions at the bottom of the page). When making adjustments, make tmp_table_size/max_heap_table_size equal Reduce your SELECT DISTINCT queries which have no LIMIT clause Performance schema should be activated for better diagnostics Consider installing Sys schema from https://github.com/mysql/mysql-sys for MySQL Before changing innodb_log_file_size and/or innodb_log_files_in_group read this: https://bit.ly/2TcGgtU Variables to adjust: DON'T APPLY SETTINGS BECAUSE THERE ARE TOO MANY PROCESSES RUNNING ON THIS SERVER. OOM KILL CAN OCCUR! skip-name-resolve=1 join_buffer_size (> 5.0M, or always use indexes with JOINs) tmp_table_size (> 16M) max_heap_table_size (> 16M) table_definition_cache (400) > 428 or -1 (autosizing if supported) performance_schema=ON key_buffer_size (~ 24M) innodb_log_file_size should be (=16M) if possible, so InnoDB total log files size equals 25% of buffer pool size. # end of MySQLTuner command #2 ################################################### # here we can see the databases and count number of tables if this matters MariaDB [psa]> show databases; +--------------------+ | Database | +--------------------+ | apsc | | information_schema | | mysql | | performance_schema | | phpmyadmin | | psa | | roundcubemail | +--------------------+ 7 rows in set (0.001 sec) MariaDB [psa]> SELECT COUNT(*) FROM information_schema.tables WHERE table_schema = 'apsc'; +----------+ | COUNT(*) | +----------+ | 23 | +----------+ 1 row in set (0.003 sec) MariaDB [psa]> SELECT COUNT(*) FROM information_schema.tables WHERE table_schema = 'mysql'; +----------+ | COUNT(*) | +----------+ | 31 | +----------+ 1 row in set (0.001 sec) MariaDB [psa]> SELECT COUNT(*) FROM information_schema.tables WHERE table_schema = 'phpmyadmin'; +----------+ | COUNT(*) | +----------+ | 19 | +----------+ 1 row in set (0.001 sec) MariaDB [psa]> SELECT COUNT(*) FROM information_schema.tables WHERE table_schema = 'psa'; +----------+ | COUNT(*) | +----------+ | 208 | +----------+ 1 row in set (0.001 sec) MariaDB [psa]> SELECT COUNT(*) FROM information_schema.tables WHERE table_schema = 'roundcubemail'; +----------+ | COUNT(*) | +----------+ | 17 | +----------+ 1 row in set (0.001 sec) # Thank you, Dragos

3 6

[Maria-discuss] command history - ignore cmds including keywords - ?
by lejeczek 06 Jan '23

06 Jan '23

Hi guys. I'm sroogling and the Internet says there should be a couple of ways to tell mySQL, MariaDB too I'd hope, to ignore command lines which contain certain keywords. So I tried bash/shell variable and also put some things into '.my.cnf' but to no avail. Does anybody know how to achieve such a basic, I'd like to think, thing? many thanks, L.

1 0

[Maria-discuss] MariaDB 10.5.18: Performance-Problems with CONCAT
by Johannes Ody 05 Jan '23

05 Jan '23

I'm german. Please excuse my bad english. MariaDB version 10.5.18 is much slower than version 10.5.16 in string-manipulation (CONCAT). In version 10.5.16 my code in the bottom needs for 800 records in tmp_tartikel_live 1-2 seconds. In version 10.5.18 my code needs for 800 records in tmp_tartikel_live 20-30 seconds. In version 10.5.16 my code needs for 26000 records in tmp_tartikel_live 5-6 minutes. It is ok. In version 10.5.18 my code needs for 26000 records in tmp_tartikel_live more than 2 hours and was terminating by the system and was not ready. The execution-time glows much more than linear. The calling script is internal for maintenance-work at night. The purpose of this code is to build our search-tables in MySQL (concordance). The code must work for strings with special characters in the coding-systems html (è), ansi and utf-8. In german and france we have the special characters: ß ü ö äàá èé and so on. I have found other users with performance-problems in MariaDB version 10.5.18, and they also use CONCAT: https://dba.stackexchange.com/questions/284073/query-performance-drop-after… My code is the following: /*#JODY_20221010 Die Datenbank muss fuer diesen Code auf Kollektion=latin1_swedish_ci eingestellt sein. ALTER DATABASE d03a5b1c COLLATE latin1_swedish_ci; Das CHARACTER SET scheint nicht so wichtig zu sein. */ /* #JODY_20211228 (ACHTUNG): Diese Datei muss ASCII-Codiert sein (nicht UTF8) Funktion zum Loeschen von HTML-Tags. Kann nur vom browser aus installiert werden. * / DROP PROCEDURE IF EXISTS mysql_log;*/ DROP FUNCTION IF EXISTS mysql_striptags; DROP FUNCTION IF EXISTS mysql_replace_utf8_sonderzeichen; DROP FUNCTION IF EXISTS mysql_replace_single_char; DROP FUNCTION IF EXISTS mysql_replace_char; DROP FUNCTION IF EXISTS mysql_replace_umlaute; /*DROP FUNCTION IF EXISTS mysql_delete_fuellwoerter;*/ DELIMITER $$ /*CREATE PROCEDURE mysql_log(strText VARCHAR(255)) BEGIN INSERT INTO debugout(cText) VALUES (strText); END$$*/ CREATE FUNCTION mysql_striptags(strParam TEXT) RETURNS TEXT DETERMINISTIC BEGIN DECLARE str TEXT; DECLARE posOpen INT; DECLARE posClose INT; SET str = strParam; loop1: LOOP SET posOpen = LOCATE("<", str); SET posClose = LOCATE(">", str, posOpen); /*#JODY_20211228 Wenn posOpen 0 ist, dann ist posClose auch immer 0.*/ IF posClose = 0 THEN LEAVE loop1; END IF; SET str = CONCAT(LEFT(str, posOpen - 1), " ", MID(str, posClose + 1)); END LOOP loop1; RETURN str; END$$ /*#JODY_20220201: Die Moeglichkeit zur URL-Erzeugung mit UTF8-Sonderzeichen besteht darin, dass ein Anwender Strings aus einem Eingabefeld in die Zwischenablage kopiert und dann im URL-Feld des Browsers einfuegt. Dann stehen in der URL z.B. fuer ä CONCAT(CHAR(195), CHAR(164)) Das Problem ist also die Eingabe von Sonderzeichen im URL-Feld des Browsers.*/ CREATE FUNCTION mysql_replace_utf8_sonderzeichen(strParam TEXT) RETURNS TEXT DETERMINISTIC BEGIN DECLARE str TEXT; DECLARE nPos INT; DECLARE nOrd INT; DECLARE strChar VARCHAR(2); SET str = strParam; SET nPos = 1; loop_for: LOOP SET nPos = LOCATE(CHAR(195), str, nPos); /* ACHTUNG (#JODY_20220201): Hier kommen auch Positionen auf ein einfaches a zurueck. Liegt an MySQL. Diese brauche ich hier zwar nicht. Aber der Code kann damit umgehen. Durch das LOCATE spare ich mir aber fuer die grosse Menge an Zeichen die Schleifendurchlaeufe.*/ IF nPos = 0 THEN LEAVE loop_for; END IF; SET strChar = MID(str, nPos, 1); SET nPos = nPos + 1; IF ORD(strChar) != 195 THEN ITERATE loop_for; END IF; SET strChar = MID(str, nPos, 1); SET nOrd = ORD(strChar); IF nOrd >= 132 AND nOrd <= 188 THEN SET str = REPLACE(str, CONCAT(CHAR(195), strChar), CHAR(nOrd + 64)); SET nPos = nPos + 1; END IF; END LOOP; RETURN str; END$$ /* ACHTUNG (#JODY_20220120): Da strNewStr auch nur Blanks enthalten darf/kann, kann hier nicht mit CHAR(2) gearbeitet werden. Variablen vom Typ CHAR(x) waeren bei einem Wert von z.B. " " leer (Laenge 0), da die Laenge sich aus dem ersten Zeichen von rechts, da kein Blank ist, ergibt. Es sind gewissermassen Fortran-Strings, die ja auch so arbeiten. VARCHAR sind dagegen C-Strings, die 0-terminiert sind. */ CREATE FUNCTION mysql_replace_single_char(strParam TEXT, nChr INT, strName CHAR(10), strNewStr VARCHAR(2)) RETURNS TEXT DETERMINISTIC BEGIN DECLARE str TEXT; DECLARE strNewStrTmp VARCHAR(2); DECLARE strChar195 VARCHAR(2); DECLARE nPosEnd INT; SET strNewStrTmp = strNewStr; /*ACHTUNG (#JODY_20220120): Nach meinem aktuellen Kenntnisstand koennen Parameter nicht geaendert werden.*/ IF strNewStrTmp = "<" THEN SET strNewStrTmp = LEFT(strName, 1); END IF; SET str = REPLACE(strParam, CONCAT("&", strName, ";"), strNewStrTmp); IF nChr <= 255 THEN SET str = REPLACE(str, CHAR(nChr), strNewStrTmp); END IF; SET str = REPLACE(str, CONCAT("&#", CONVERT(nChr, CHAR), ";"), strNewStrTmp); RETURN str; END$$ CREATE FUNCTION mysql_replace_char(strParam TEXT, nChrMin INT, nChrMax INT, strNamesExt VARCHAR(40), strNewStr CHAR(1)) RETURNS TEXT DETERMINISTIC BEGIN DECLARE str TEXT; DECLARE nChr INT; DECLARE strNames VARCHAR(40); DECLARE nPosStart INT; DECLARE nPosEnd INT; DECLARE bUseNames TINYINT; DECLARE strName VARCHAR(40); DECLARE strNewStrUpper CHAR(1); SET str = strParam; SET nChr = nChrMin; IF strNamesExt != "" THEN /*#JODY_20211229 In MySQL gibt es in Stored Procedures keine Array-Unterstuetzung. s. https://forums.mysql.com/read.php?98,406197,406216*/ SET strNames = CONCAT("grave;acute;circ;", strNamesExt); /*#JODY_20220408 Dieser Code ist fuer die Sonderzeichen à usw. gedacht. Nicht fuer &grave;*/ SET bUseNames = 1; SET strNewStrUpper = UPPER(strNewStr); SET nPosStart = 1; ELSE SET bUseNames = 0; END IF; loop_for: LOOP IF bUseNames != 0 THEN SET nPosEnd = LOCATE(";", strNames, nPosStart); SET strName = MID(strNames, nPosStart, nPosEnd - nPosStart + 1); /*#JODY_20211229 Das ; will ich mit haben.*/ SET str = REPLACE(str, CONCAT("&", strNewStr, strName), strNewStr); SET str = REPLACE(str, CONCAT("&", strNewStrUpper, strName), strNewStr); /*SET strNames = MID(strNames, nPos + 1);*/ SET nPosStart = nPosEnd + 1; /*#JODY_20211229 So ersprare ich mir dieses MID.*/ END IF; SET str = REPLACE(str, CONCAT("&#", CONVERT(nChr, CHAR), ";"), strNewStr); SET str = REPLACE(str, CHAR(nChr), strNewStr); /*#JODY_20211229 Diese Funktion wird nur fuer Umlaute und nur fuer die kleinen augerufen. Diese liegen zwischen à und ü.*/ SET str = REPLACE(str, CONCAT("&#", CONVERT(nChr - 32, CHAR), ";"), strNewStr); SET str = REPLACE(str, CHAR(nChr - 32), strNewStr); IF nChr >= nChrMax THEN LEAVE loop_for; END IF; SET nChr = nChr + 1; END LOOP; RETURN str; END$$ CREATE FUNCTION mysql_replace_umlaute(strParam TEXT) RETURNS TEXT DETERMINISTIC BEGIN DECLARE str TEXT; DECLARE nPos INT; DECLARE nChr INT; SET str = mysql_replace_utf8_sonderzeichen(strParam); /* ACHTUNG (#JODY_20220201): Die UTF8-Sonderzeichen muessen hier ganz oben behandelt werden. Sie werden in ASCII-Sonderzeichen konvertiert, die ja nachfolgend auch noch wieder konvertiert werden. So kann ich das aber allgemein gueltig fuer alle UTF8-Sonderzeichen abhandeln.*/ SET str = REPLACE(LOWER(str), "make-up", "makeup"); /*#JODY_20220315 Make-Up soll intern als ein Wort behandelt werden.*/ /*#JODY_20220120 Die vor- und nachlaufenden Blanks werden benoetigt, damit der Wortanfaeng/-ende richtig und leicht erkannt wird. */ SET str = CONCAT(" ", mysql_striptags(str), " "); SET str = mysql_replace_char(str, 224, 230, "tilde;uml;ring;elig;", "a"); SET str = mysql_replace_char(str, 232, 235, "uml;", "e"); SET str = mysql_replace_char(str, 236, 239, "uml;", "i"); SET str = mysql_replace_char(str, 242, 246, "tilde;uml;slash;", "o"); /*#JODY_20211228 So brauche ich den Ignore-Parameter in mysql_replace_char() nicht mehr. × und ÷ sollen hier nicht beachtet werden.*/ SET str = mysql_replace_single_char(str, 216, "Oslash", "o"); SET str = mysql_replace_single_char(str, 248, "oslash", "o"); SET str = mysql_replace_char(str, 249, 252, "uml;", "u"); SET str = mysql_replace_single_char(str, 223, "szlig", "ss"); SET str = REPLACE(str, "ae", "a"); SET str = REPLACE(str, "oe", "o"); SET str = REPLACE(str, "ue", "u"); SET str = mysql_replace_single_char(str, 191, "iquest", ""); /*#JODY_20211228 françois*/ SET str = mysql_replace_single_char(str, 199, "Ccedil", "<");/*#JODY_20211228 françois*/ SET str = mysql_replace_single_char(str, 231, "ccedil", "<");/*#JODY_20211228 françois*/ SET str = mysql_replace_single_char(str, 241, "ntilde", "<");/*#JODY_20211228 porteño*/ SET str = mysql_replace_single_char(str, 215, "times", "x"); SET str = mysql_replace_single_char(str, 160, "nbsp", " "); SET str = mysql_replace_single_char(str, 178, "sup2", "2"); /*#JODY_20211228 Hochgestellte 2 z.B. bei dem Hersteller dsquared²*/ SET str = mysql_replace_single_char(str, 179, "sup3", "3"); /*#JODY_20211228 Hochgestellte 3 z.B. "wella care³ balance clean anti"*/ SET str = mysql_replace_single_char(str, 185, "sup1", ""); /*#JODY_20211228 Hochgestellte 1; wird aber nicht benoetigt.*/ SET str = mysql_replace_single_char(str, 8216, "lsquo", "");/*#JODY_20211228 j‘adore*/ SET str = mysql_replace_single_char(str, 8217, "rsquo", "");/*#JODY_20211228 j’adore*/ SET str = REPLACE(str, "'", ""); /*#JODY_20211228 l'oreal*/ SET str = mysql_replace_single_char(str, 34/*"*/, "quot", "");/*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 169, "copy", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 173, "shy", ""); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 174, "reg", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 176, "deg", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 183, "middot", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 8194, "ensp", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 8218, "sbquo", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 8226, "bull", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 8230, "hellip", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 8364, "euro", "euro"); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 8482, "trade", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 8722, "minus", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = REPLACE(str, "̈", ""); /*#JODY_20211228 Beispiel: "ascorbinsaure natürliches aroma"; Bei "ä" wird ein ä angezeigt.*/ SET str = mysql_replace_single_char(str, 60, "lt", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 62, "gt", " "); /*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 171, "laquo", " ");/*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 187, "raquo", " ");/*#JODY_20211228 Ist fuer die Suche nicht relevant.*/ SET str = mysql_replace_single_char(str, 189, "frac12", "");/*#JODY_20211228 "mit ca ½ liter"*/ /*#JODY_20211228 (ACHTUNG): Prinzipiell soll ´ durch ein Blank ersetzt werden. Nur bei loreal ist dies auf Grund des Eigennamens nicht erwuenscht.*/ SET str = mysql_replace_single_char(str, 96, "grave", " ");/*#JODY_20220408"*/ /*SET str = REPLACE(str, "l´oreal", "loreal"); #JODY_20220408*/ SET str = mysql_replace_single_char(str, 180, "acute", " ");/*#JODY_20211228 "save´n" oder "rock´n"*/ SET str = REPLACE(str, "&", " "); /*#JODY_20220119 Es exisztieren so viele Begriffe, die in [] eingeklammert sind. z.B. [iln48006]*/ SET str = REPLACE(str, "[", " "); SET str = REPLACE(str, "]", " "); SET str = REPLACE(str, "#", " "); SET str = REPLACE(str, "*", " "); SET str = REPLACE(str, "&", " "); SET str = REPLACE(str, "%", " "); SET str = REPLACE(str, "|", " ");/*#JODY_20220316*/ SET str = REPLACE(str, ".", " "); SET str = REPLACE(str, ":", " "); SET str = REPLACE(str, ",", " "); SET str = REPLACE(str, ";", " "); SET str = REPLACE(str, "?", " "); SET str = REPLACE(str, "!", " "); SET str = REPLACE(str, "/", " "); SET str = REPLACE(str, "\\", " "); /*#JODY_20220120 Macht mir z.B. beim Suchbegriff "wax\" die SQL-Anweisung kaputt.*/ SET str = REPLACE(str, "-", " "); SET str = REPLACE(str, "+", " "); SET str = REPLACE(str, "=", " "); SET str = REPLACE(str, "\r", " "); SET str = REPLACE(str, "\n", " "); SET str = REPLACE(str, "\t", " "); SET str = REPLACE(str, "(", " "); SET str = REPLACE(str, ")", " "); /* #JODY_20220121 Erstmal nicht. Die Anwender suchen meistens nach Woertern, wo ein loeschen dieser Buchstaben das Suchergebnis eigentlich verschlechtert, da weniger Zeichenuebereinstimmungen bei Teilwoertern gefunden werden. In Teilwoertern #JODY_20220120 Dies soll die Menge der Wortredundanzen verringern. z.B. zugewandte/zugewandt* / SET str = REPLACE(str, "em ", " "); SET str = REPLACE(str, "en ", " "); SET str = REPLACE(str, "es ", " "); SET str = REPLACE(str, "er ", " "); SET str = REPLACE(str, " sie ", " "); /*#JODY_20220120 Dies ist so noetig, da "sie" durch das naechste REPLACE zu "si" wird und eine Gleichbehandlung von "sie" und "si" wegen der vielen Suchen nach "si" nicht erwunescht ist. Ausserdem macht die Suche nach "sie" eigentlich auch keinen Sinn.* / SET str = REPLACE(str, "e ", " "); SET str = REPLACE(str, "ig ", " ");*/ /*#JODY_20211229 Bisher koennen durchaus mehrere Leerzeichen hintereinander sein. Diese jetzt zu einem zusammenstreichen.*/ loop1: LOOP SET nPos = LOCATE(" ", str); IF nPos = 0 THEN LEAVE loop1; END IF; SET str = REPLACE(str, " ", " "); END LOOP loop1; SET str = TRIM(str); /*#JODY_20220120 Die vor- und nachlaufenden Blanks wieder loeschen. Wurde nur eingefuegt, damit der Wortanfaeng/-ende richtig und leicht erkannt wird. */ RETURN str; END$$ DELIMITER ; CREATE TABLE tmp_tartikel_live ( kArtikel INT UNSIGNED, cArtNr VARCHAR(31), cSeo VARCHAR(255), cSeoU TEXT, cBeschreibung TEXT, cBeschreibungU TEXT, cName VARCHAR(255), cSuchbegriffe TEXT, cKurzBeschreibung TEXT, kurztyp TEXT, kurzserie TEXT, kurzname TEXT ) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci; SELECT tmp_tartikel_live.kArtikel, tmp_tartikel_live.cArtNr, tmp_tartikel_live.cSeo, tmp_tartikel_live.cBeschreibung, CONCAT(" ", mysql_replace_umlaute(tmp_tartikel_live.cName), " ") AS cNameU, CONCAT(" ", mysql_replace_umlaute(tmp_tartikel_live.cSuchbegriffe), " ") AS cSuchbegriffeU, CONCAT(" ", mysql_replace_umlaute(tmp_tartikel_live.cKurzBeschreibung), " ") AS cKurzBeschreibungU, CONCAT(" ", mysql_replace_umlaute(tmp_tartikel_live.cBeschreibung), " ") AS cBeschreibungU, CONCAT(" ", mysql_replace_umlaute(tmp_tartikel_live.cSeo), " ") AS cSeoU, CONCAT(" ", mysql_replace_umlaute(tmp_tartikel_live.kurztyp), " ") AS kurztypU, CONCAT(" ", mysql_replace_umlaute(tmp_tartikel_live.kurzserie), " ") AS kurzserieU, CONCAT(" ", mysql_replace_umlaute(tmp_tartikel_live.kurzname), " ") AS kurznameU FROM tmp_tartikel_live This code prepare article-text for search in. Is this problem known or is it new. I hope, I do it right in this way. Johannes Ody

3 3

[Maria-discuss] problems getting MariaDB to start after install
by Tim McConnell 03 Jan '23

03 Jan '23

Hello list, I have installed and re-installed MariaDB trying to get prelude to work and I'm at a loss. When I try to run 'sudo systemctl start mariadb.service' I get these errors: Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xeu mariadb.service" for details. so I read the KB and found I'm supposed to use 'sudo systemctl status mariadb.socket' which gives this: ● mariadb.socket - MariaDB 10.6.11 database server (socket activation) Loaded: loaded (/lib/systemd/system/mariadb.socket; static) Active: active (listening) since Thu 2022-12-29 18:39:25 CST; 26s ago Until: Thu 2022-12-29 18:39:25 CST; 26s ago Triggers: ● mariadb.service Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Listen: @mariadb (Stream) /run/mysqld/mysqld.sock (Stream) [::]:3306 (Stream) Tasks: 0 (limit: 8190) Memory: 4.0K CPU: 2ms CGroup: /system.slice/mariadb.socket and then if I try to run 'sudo mysqlcheck -A' I'll get this error: mysqlcheck: Got error: 2013: Lost connection to server at 'handshake: reading initial communication packet', system error: 104 when trying to connect I then check the status of the socket and get this output: sudo systemctl status mariadb.socket × mariadb.socket - MariaDB 10.6.11 database server (socket activation) Loaded: loaded (/lib/systemd/system/mariadb.socket; static) Active: failed (Result: service-start-limit-hit) since Thu 2022-12-29 18:4> Duration: 1min 11.173s Triggers: ● mariadb.service Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Listen: @mariadb (Stream) /run/mysqld/mysqld.sock (Stream) [::]:3306 (Stream) CPU: 2ms I then ran 'sudo journalctl -n 20 -u mariadb.service' (as per the kb) and get: Dec 29 19:12:45 DebianTim mariadbd[3660996]: 2022-12-29 19:12:45 0 [Note] /usr/sbin/mariadbd (server 10.6.11-MariaDB-1) starting as process 3660996 ... Dec 29 19:12:45 DebianTim systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Dec 29 19:12:45 DebianTim systemd[1]: mariadb.service: Failed with result 'exit-code'. Dec 29 19:12:45 DebianTim systemd[1]: Failed to start MariaDB 10.6.11 database server. I then found this in my logs: 2022-12-29 19:12:45 0 [Warning] Plugin 'OQGRAPH' is of maturity level gamma while the server is stable 2022-12-29 19:12:45 0 [Note] CONNECT: Version 1.07.0002 March 22, 2021 2022-12-29 19:12:45 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 2022-12-29 19:12:45 0 [Note] InnoDB: Number of pools: 1 2022-12-29 19:12:45 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-12-29 19:12:45 0 [Note] InnoDB: Using liburing 2022-12-29 19:12:45 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2022-12-29 19:12:45 0 [Note] InnoDB: Completed initialization of buffer pool 2022-12-29 19:12:45 0 [Note] InnoDB: 128 rollback segments are active. 2022-12-29 19:12:45 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-12-29 19:12:45 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2022-12-29 19:12:45 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2022-12-29 19:12:45 0 [Note] InnoDB: 10.6.11 started; log sequence number 33836; transaction id 4 2022-12-29 19:12:45 0 [Note] Plugin 'FEEDBACK' is disabled. 2022-12-29 19:12:45 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2022-12-29 19:12:45 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded 2022-12-29 19:12:45 0 [Note] InnoDB: Buffer pool(s) load completed at 221229 19:12:45 2022-12-29 19:12:45 0 [Warning] You need to use --log-bin to make -- expire-logs-days or --binlog-expire-logs-seconds work. 2022-12-29 19:12:45 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 2022-12-29 19:12:45 0 [Note] Using systemd activated socket host :: port 3306 2022-12-29 19:12:45 0 [Note] Using systemd activated unix socket /run/mysqld/mysqld.sock 2022-12-29 19:12:45 0 [Note] Using systemd activated unix socket @mariadb 2022-12-29 19:12:45 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.db' doesn't exist 2022-12-29 19:12:45 0 [ERROR] Aborting Warning: Memory not freed: 280 So, how do I get this to work? I even tried the apparmor suggestion from the KB and it didn't work, I even tried stopping apparmor service completely and still couldn't get it to work. I'm using Debian testing (Bookworm) with Kernel version 6.0.0-6-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.12-1 (2022-12-09) x86_64 GNU/Linux and MariaDB 10.6.11 from the Debian repository. Thanks in advance for any help. -- Tim McConnell <tmcconnell168(a)gmail.com>

4 10

[Maria-discuss] debian 11 + mariadb remote connections
by Aaron Axelsen 29 Dec '22

29 Dec '22

Howdy all! I'm having trouble figuring out why a new install on a debian 11 box of mariadb 10.10 is not allowing remote connections. I'm really at a loss for what's going on. I've adjusted the bind address and made sure it's setup for remote connections. From this box, I am able to access mysql using 127.0.0.1, 192.168.0.143 or the external IP without any issue. When trying to connect from any other box, it's acting like it's blocked by the firewall. * iptables is what I generally use but i've cleared out all rules, flushed all tables, and all policies are set to accept. * There is no firewall running from my cloud host - verified with their support team. * Other services are connecting just fine externally, which would really point towards an issues specific with mariadb. MariaDB is currently binding to app ipv4 and ipv6 interfaces. I've tried having only bind to ipv4, changing the default port to something other than 3306. I even went as far as spinning up a test server, same config and it's working as expected. This server is setup for email - so it's also running postfix, dovecot, rspam, redis and apache. Any suggestions or thoughts are greatly appreciated! -- Aaron Axelsen

3 3

[Maria-discuss] MySQL Workbench Issue
by Software Info 28 Dec '22

28 Dec '22

Hi All, I have a very strange problem here. I have mariadb 10.6.10 running on FreeBSD 13.1. I have SSL enabled globally. When I use MySQL workbench to log on from Windows 10 machines, I can authenticate but when I use the same credentials to log on from a Windows 2012 server, I cannot. I get the error user access denied. The credential is configured to log on from anywhere. Is there some kind of SSL/TLS incompatibility in Windows 2013 that anyone knows of? Any help would be appreciated. Best regards, SI

2 1

[Maria-discuss] Code of Conduct
by Ian Gilfillan 23 Dec '22

23 Dec '22

In the light of recent events, we're implementing a Code of Conduct. Details at https://mariadb.org/going-for-a-code-of-conduct/ - comments are welcome!

10 24

[Maria-discuss] DBMS vs Storage Engine Alone
by Jonathan M. Wilbur 20 Dec '22

20 Dec '22

Sorry to ask this question here, since it is not strictly MariaDB-related, but I need the knowledge of people that develop with databases: is there significant overhead to using a DBMS versus a storage engine directly? I have a project for which speed / latency is very important, and I was wondering if I could make significant performance gains by using a storage engine (such as WiredTiger, RocksDB, LevelDB, etc.) directly instead of using a DBMS (like MariaDB). More concretely, are there any studies out there on this to give me some objective numbers on this? Assume it is over a local loopback connection, so pretty much only the overhead of the networking itself would apply. Thank you in advance, - Jonathan M. Wilbur

4 3

[Maria-discuss] flush tables with read lock blocks
by Alex 13 Dec '22

13 Dec '22

Hi, I'm using mariadb-10.5.18-1.fc37.x86_64 on fedora37 set up as a master server. There are currently two or three slaves configured and operating properly. I'm trying to add another slave, and for some reason when I try to flush tables with read lock, then dump the databases to be transferred to the new slave, mysqldump just prints: -- Connecting to localhost... At first I didn't realize it, but soon the database stopped responding to all clients until I released the lock with "unlock tables". I'm following these directions: https://mariadb.com/kb/en/setting-up-replication/ What could I be doing wrong? Here are the my.cnf options that I believe could be related to my issue. Any ideas greatly appreciated. The server has 128GB of RAM. [mysqld] sql_mode=ONLY_FULL_GROUP_BY character-set-client-handshake = FALSE character-set-server = utf8mb4 collation-server = utf8mb4_unicode_ci max_connections=1000 replicate_do_db='repdb' replicate_do_db='sbclient' port = 3306 socket = /var/lib/mysql/mysql.sock skip-external-locking key_buffer_size = 256M max_allowed_packet = 512M join_buffer_size = 2M read_rnd_buffer_size = 4M myisam_sort_buffer_size = 64M query_cache_size = 400000000 query_cache_type = 1 query_cache_strip_comments = 1 relay_log_space_limit = 500M relay_log_purge = 1 log-slave-updates = 1 local_infile = OFF binlog_format = ROW max_heap_table_size = 2048M tmp_table_size = 2048M relay-log=myserver-relay-bin log_bin = /var/log/mariadb/mysql-bin.log log_warnings = 1 expire_logs_days = 2 max_binlog_size = 500M plugin_load=server_audit=server_audit.so plugin_load_add = query_response_time server_audit_events=connect,query server_audit_file_path = /var/log/mariadb/server_audit.log server_audit_file_rotate_size = 1G server_audit_file_rotations = 1 slow-query-log = 1 slow-query-log-file = /var/log/mariadb/mariadb-slow.log long_query_time = 1 log_error = /var/log/mariadb/mariadb-error.log skip-networking=0 binlog_format=mixed server-id = 590

2 2

Re: [Maria-discuss] Maria-db refuses to start
by Jogchum Reitsma 12 Dec '22

12 Dec '22

Op 08-11-2022 om 13:04 schreef Marko Mäkelä: > Hi Jogchum, > > On Tue, Nov 8, 2022 at 1:21 PM Jogchum Reitsma > <jogchum.reitsma(a)gmail.com> wrote: > [...] >> 2022-11-08 12:06:17 0 [Warning] 'innodb-file-format' was removed. It does nothing now and exists only for compatibility with old my.cnf files. >> (repeated several times) >> 2022-11-08 12:06:17 0 [ERROR] /usr/local/mariadb-10.6.10-linux-systemd-x86_64/bin/mariadbd: unknown option '--skip-locking' >> 2022-11-08 12:06:17 0 [ERROR] Aborting > Was that the end of the output? No shutdown message from InnoDB, like this? > > 2022-11-08 14:03:03 0 [Note] InnoDB: Shutdown completed; log sequence > number 2150107; transaction id 3085 > > If there was no output like that, you should remove any line that says > "skip_locking" or "skip-locking" from the configuration file and > retry. > > Marko Yes, that was indeed the end of the output. The skip-locking statement was not in /etc/my.cnf, but inmy.cnf in my home dir. Commented it out and now this complaint disappeared. But now I get #################################################################### 2022-11-08 13:37:32 0 [Note] InnoDB: Compressed tables use zlib 1.2.12 2022-11-08 13:37:32 0 [Note] InnoDB: Number of pools: 1 2022-11-08 13:37:32 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-11-08 13:37:32 0 [Note] InnoDB: Using Linux native AIO 2022-11-08 13:37:32 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2022-11-08 13:37:32 0 [Note] InnoDB: Completed initialization of buffer pool 2022-11-08 13:37:32 0 [Note] InnoDB: 128 rollback segments are active. 2022-11-08 13:37:32 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-11-08 13:37:32 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2022-11-08 13:37:32 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2022-11-08 13:37:32 0 [Note] InnoDB: 10.6.10 started; log sequence number 578191791; transaction id 2935782 2022-11-08 13:37:32 0 [Note] InnoDB: Loading buffer pool(s) from /home/jogchum/mysql/ib_buffer_pool 2022-11-08 13:37:32 0 [Note] Plugin 'FEEDBACK' is disabled. 2022-11-08 13:37:32 0 [Warning] 'innodb-file-format' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2022-11-08 13:37:33 0 [Note] Server socket created on IP: '0.0.0.0'. 2022-11-08 13:37:33 0 [ERROR] Can't start server : Bind on unix socket: No such file or directory 2022-11-08 13:37:33 0 [ERROR] Do you already have another server running on socket: /var/run/mysql/mysql.sock ? 2022-11-08 13:37:33 0 [ERROR] Aborting Warning: Memory not freed: 280 ########################################################################## (again no further output). /var/run/mysql/mysql.sock odoes not exeist, and "pgrep mariadbd", "pgrep mysql" and "pgrep mysqld" show nothing, so no serer is running anymore. ss -a | grep 3306 or ss -a | grep /var/run/mysql also gives nothing, so it seems there are no processes using that port. We're getting closer it seems, but not quite there yet... regards, Jogchum

7 48

[Maria-discuss] Statistics are not being updated?
by Colin Charles 08 Dec '22

08 Dec '22

Hi, Any reason statistics stopped being updated in October? https://mariadb.org/statistics/ Would be great if this got fixed, thanks cheers, -c -- Colin Charles, http://bytebot.net/blog/ twitter: @bytebot | skype: colincharles "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi

2 1

[Maria-discuss] Followup on MDEV-25625, still present in 10.5.16
by Chris Ross (cross2) 17 Nov '22

17 Nov '22

Hello all. I came across MDEV-25625 while looking for that same problem. It was closed, I think because the reporter didn’t get back to it, but I’m now seeing the same. I’ve added a comment, but I don’t know if commenting on a closed issue will notify anyone. Can anyone comment/re-open that issue? I don’t want to file a duplicate. Thank you. https://jira.mariadb.org/browse/MDEV-25625 - Chris

2 3

[Maria-discuss] subscribe
by Surya 15 Nov '22

15 Nov '22

Hello , -- Best regards, Surya mailto:surya@fastmail.in

1 0

[Maria-discuss] (no subject)
by Surya 15 Nov '22

15 Nov '22

Hello , -- Best regards, Surya mailto:surya@fastmail.in

1 0

[Maria-discuss] mariadb-10.3.37 strips "collate" from "show create table"
by Reindl Harald 10 Nov '22

10 Nov '22

mariadb-10.3.36 versus mariadb-10.3.37 in the past every field contained "collate latin1_german1_ci" and after this point-update collation is only part of the output if it's different then the tables default collation surely, i can update everything to mariadb-10.3.37 and rewrite all this tests in the hope the next point-update don't restore the old behavior but it's really a bad style --------------------------------------------------------------------------------------------------------------------- CALLER: '/autotests/custom/phpincludes_mysql.php:306': --------------------------------------------------------------------------------------------------------------------- --- old_9bb3995c3244abfff522da086526e88b5a8a81f1e7cf672d8343f20d.txt 2022-11-10 01:03:12.366665303 +0100 +++ new_53033703b16454931e7c7f62ef923229ca8183aff6f6fa017cdb44bd.txt 2022-11-10 01:03:12.366665303 +0100 @@ -1,14 +1,14 @@ create table `test_table` (`test_id` mediumint(7) unsigned not null auto_increment, -`char_char` char(200) collate latin1_german1_ci default null, +`char_char` char(200) default null, `char_date` date default null, `char_datetime` datetime default null, -`char_longtext` longtext collate latin1_german1_ci default null, -`char_mediumtext` mediumtext collate latin1_german1_ci default null, -`char_text` text collate latin1_german1_ci default null, +`char_longtext` longtext default null, +`char_mediumtext` mediumtext default null, +`char_text` text default null, `char_time` time default null, `char_timestamp` datetime default null, -`char_tinytext` tinytext collate latin1_german1_ci default null, -`char_varchar` varchar(200) collate latin1_german1_ci default null, +`char_tinytext` tinytext default null, +`char_varchar` varchar(200) default null, `number_bigint` bigint(200) unsigned default null, `number_double` double unsigned default null, `number_float` double unsigned default null,

1 0

[Maria-discuss] Maria-db refuses to start
by Jogchum Reitsma 08 Nov '22

08 Nov '22

Hi, I am on OpenSuse Tumbleweed, rolling distro. Since some snapshots of Tumbleweed my mariadb does not start at system start. I don't use the mariadb databases a lot, so I didn't notice it immediately. Hence I'm unsure when the problem occurred first time. When trying to start it manually, I got the message [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.8. Searching that message, I saw a post on https://bbs.archlinux.org/viewtopic.php?id=259364 Like me, he had a non-default location for the databases configured in /etc/my.cnf. The solution that worked for him was to change that to another location in my.cnf, starting the database (which now succeeded), and copy the existing databases to that new location. So I decided to mimic that: commented out the existing database location, entered an new one, and started the database server (as root) with systemctl start mariadb After a while, the new location is created (owned by mysql:root) and populated: l mysql_recover totaal 111048 drwx------ 6 mysql root 243 2 okt 21:33 ./ drwxr-xr-x 225 jogchum users 16384 2 okt 21:26 ../ -rw-rw---- 1 mysql mysql 417792 2 okt 21:27 aria_log.00000001 -rw-rw---- 1 mysql mysql 52 2 okt 21:27 aria_log_control -rw-rw---- 1 mysql mysql 942 2 okt 21:27 ib_buffer_pool -rw-rw---- 1 mysql mysql 12582912 2 okt 21:27 ibdata1 -rw-rw---- 1 mysql mysql 100663296 2 okt 21:27 ib_logfile0 drwx------ 2 mysql mysql 4096 2 okt 21:27 mysql/ -rw-rw---- 1 root root 14 2 okt 21:27 mysql_upgrade_info drwx------ 2 mysql mysql 28 2 okt 21:27 performance_schema/ drwx------ 2 mysql mysql 8192 2 okt 21:27 sys/ drwx------ 2 mysql mysql 28 2 okt 21:27 test/ But unlike the posting at bbs.archlinux.org just mentioned, the server crashed again, now with the following messages in journalctl: ################################################################################# journalctl -xeu mariadb.service A start job for unit mariadb.service has finished with a failure. The job identifier is 2782226 and the job result is failed. okt 02 21:20:47 linux-mkay systemd[1]: Starting MariaDB database server... Subject: A start job for unit mariadb.service has begun execution Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit mariadb.service has begun execution. The job identifier is 2790830. okt 02 21:20:47 linux-mkay mysql-systemd-helper[44977]: 2022-10-02 21:20:47 0 [Note] /usr/sbin/mysqld (server 10.8.3-MariaDB) starting as process 44977 ... okt 02 21:20:48 linux-mkay systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Subject: Unit process exited Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel An ExecStart= process belonging to unit mariadb.service has exited. The process' exit code is 'exited' and its exit status is 1. okt 02 21:20:48 linux-mkay systemd[1]: mariadb.service: Failed with result 'exit-code'. Subject: Unit failed Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel The unit mariadb.service has entered the 'failed' state with result 'exit-code'. okt 02 21:20:48 linux-mkay systemd[1]: Failed to start MariaDB database server. Subject: A start job for unit mariadb.service has failed Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit mariadb.service has finished with a failure. The job identifier is 2790830 and the job result is failed. okt 02 21:26:55 linux-mkay systemd[1]: Starting MariaDB database server... Subject: A start job for unit mariadb.service has begun execution Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit mariadb.service has begun execution. The job identifier is 2792404. okt 02 21:26:55 linux-mkay mysql-systemd-helper[45372]: Creating MySQL privilege database... okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: Two all-privilege accounts were created. okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: One is root@localhost, it has no password, but you need to okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: be system 'root' user to connect. Use, for example, sudo mysql okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: The second is mysql@localhost, it has no password either, but okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: you need to be the system 'mysql' user to connect. okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: After connecting you can set the password, if you would need to be okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: able to connect as any of these users with a password and without sudo okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: See the MariaDB Knowledgebase at https://mariadb.com/kb okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: Please report any problems at https://mariadb.org/jira okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: The latest information about MariaDB is available at https://mariadb.org/. okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: Consider joining MariaDB's strong and vibrant community: okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: https://mariadb.org/get-involved/ okt 02 21:27:17 linux-mkay mysql-systemd-helper[45468]: 2022-10-02 21:27:17 0 [Note] /usr/sbin/mysqld (server 10.8.3-MariaDB) starting as process 45468 ... okt 02 21:27:17 linux-mkay mysql-systemd-helper[45468]: 2022-10-02 21:27:17 0 [Warning] Can't create test file /home/jogchum/mysql_recover/linux-mkay.lower-test okt 02 21:27:17 linux-mkay mysql-systemd-helper[45468]: [103B blob data] okt 02 21:27:17 linux-mkay mysql-systemd-helper[45468]: 2022-10-02 21:27:17 0 [ERROR] Aborting okt 02 21:27:17 linux-mkay systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Subject: Unit process exited Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ############################################################################################ Anyone an idea why /home/jogchum/mysql_recover/linux-mkay.lower-test can't be created and how to solve that? Thanks in advance! regards, Jogchum

6 22

[Maria-discuss] Bug in incremental backups since MariaDB version 10.5.7 with mariabackup?
by Michael Rößler 02 Nov '22

02 Nov '22

Hi @ll, I am using mariabackup since 2 years. I wanted to upgrade from version 10.4.24 to 10.6.10 but I found out that incremental Backups does not work as expected because of size. Further investigation show that it is since version 10.5.7. Then I have found out that in the file xtrabackup_checkpoints the value for to_lsn is not changing in version 10.5.7 and 10.6.10. Using the command 'mysql -e "SHOW ENGINE INNODB STATUS\G" | egrep "Last check"' show that values are the same with that command and the value to_lsn in the file xtrabackup_checkpoints. Backup-commands used in test environment: mariabackup --extra-lsndir=/var/backup/full --backup --compress --stream=xbstream --user=root --password=root --target-dir=/var/backup/full > /var/backup/full/full.xbstream mariabackup --extra-lsndir=/var/backup/inc1 --backup --compress --stream=xbstream --user=root --password=root --incremental-basedir=/var/backup/full --target-dir=/var/backup/inc1 > /var/backup/inc1/inc1.xbstream mariabackup --extra-lsndir=/var/backup/inc2 --backup --compress --stream=xbstream --user=root --password=root --incremental-basedir=/var/backup/inc1 --target-dir=/var/backup/inc2 > /var/backup/inc2/inc2.xbstream mariabackup --extra-lsndir=/var/backup/inc3 --backup --compress --stream=xbstream --user=root --password=root --incremental-basedir=/var/backup/inc2 --target-dir=/var/backup/inc3 > /var/backup/inc3/inc3.xbstream Size of files compared between version 10.5.6 and 10.5.7: [root@mysqlsingle2 backup]# ls *10.5.6/*xbstream -lh -rw-r--r-- 1 root root 765K 2. Nov 13:03 full-10.5.6/full.xbstream -rw-r--r-- 1 root root 779K 2. Nov 13:06 inc1-10.5.6/inc1.xbstream -rw-r--r-- 1 root root 1,2M 2. Nov 13:16 inc2-10.5.6/inc2.xbstream -rw-r--r-- 1 root root 752K 2. Nov 13:17 inc3-10.5.6/inc3.xbstream [root@mysqlsingle2 backup]# ls -lh *10.5.7/*xbstream -rw-r--r-- 1 root root 763K 2. Nov 13:22 full-10.5.7/full.xbstream -rw-r--r-- 1 root root 723K 2. Nov 13:23 inc1-10.5.7/inc1.xbstream # added 2000 rows -rw-r--r-- 1 root root 2,1M 2. Nov 13:30 inc2-10.5.7/inc2.xbstream # added 20000 rows -rw-r--r-- 1 root root 2,2M 2. Nov 13:31 inc3-10.5.7/inc3.xbstream # added 2000 rows to_lsn in file xtrabackup_checkpoints: [root@mysqlsingle2 backup]# cat full*/*checkpoints | grep "to_lsn" to_lsn = 47455 # 10.5.6 to_lsn = 45118 # 10.5.7 [root@mysqlsingle2 backup]# cat inc1*/*checkpoints | grep "to_lsn" to_lsn = 487597 # 10.5.6 to_lsn = 45118 # 10.5.7 [root@mysqlsingle2 backup]# cat inc2*/*checkpoints | grep "to_lsn" to_lsn = 4572514 # 10.5.6 to_lsn = 45118 # 10.5.7 [root@mysqlsingle2 backup]# cat inc3*/*checkpoints | grep "to_lsn" to_lsn = 4995024 # 10.5.6 to_lsn = 45118 # 10.5.7 'Last checkpoint at' from command 'mysql -e "SHOW ENGINE INNODB STATUS\G" | egrep "Last check"': [root@mysqlsingle2 backup]# cat full*/*Last* Last checkpoint at 47455 Last checkpoint at 45118 [root@mysqlsingle2 backup]# cat inc1*/*Last* Last checkpoint at 487597 Last checkpoint at 45118 [root@mysqlsingle2 backup]# cat inc2*/*Last* Last checkpoint at 4572514 Last checkpoint at 45118 [root@mysqlsingle2 backup]# cat inc3*/*Last* Last checkpoint at 4995024 Last checkpoint at 45118 Kind regards Michael

1 0

[Maria-discuss] Galera with stunnel for rsync sst method
by John Fawcett 15 Oct '22

15 Oct '22

Hi Can someone point out or help with a step by step guide to setting up Galera to use stunnel for rsync sst? I was following the instructions here: https://mariadb.com/kb/en/introduction-to-state-snapshot-transfers-ssts/ and my main doubts are: 1. Does stunnel itself have to be configured and if so is it the same configuration on all galera nodes? 2. Does stunnel have to be running as a service on any of the galera nodes? 3. Does the configuration shown in the galera documentation [sst] tkey = /etc/my.cnf.d/certificates/client-key.pem tcert = /etc/my.cnf.d/certificates/client-cert.pem have to be done on all the galera nodes? 4. Do the above key and cert have to be the same (or have to be different) on all galera nodes? 5. more of a stunnel question, but following the link from the galera documentation to the stunnel documentation for certificate generation, https://www.stunnel.org/howto.html I got stuck on this command which no longer works on openssl 3.0.5.5: openssl gendh 2048 >> stunnel.pem Any idea on what has replaced it? Thanks for any help. John

1 0

[Maria-discuss] Migration path for unix_socket authentication plugin
by William Edwards 14 Oct '22

14 Oct '22

Hi, On MariaDB servers that were installed with >= MariaDB 10.4, I have one root user that was created as: MariaDB [(none)]> show create user 'root'@'localhost'; CREATE USER `root`@`localhost` IDENTIFIED VIA mysql_native_password USING 'invalid' OR unix_socket FWIW: The statements on https://mariadb.com/kb/en/authentication-from-mariadb-104/#description are reversed (`IDENTIFIED VIA unix_socket OR mysql_native_password USING 'invalid'` instead of `IDENTIFIED VIA mysql_native_password USING 'invalid' OR unix_socket`). On MariaDB servers that were installed with < MariaDB 10.4, I have 3 root users that were created as: MariaDB [(none)]> show create user 'root'@'localhost'; CREATE USER `root`@`localhost` MariaDB [(none)]> show create user 'root'@'::1'; CREATE USER `root`@`::1` MariaDB [(none)]> show create user 'root'@'127.0.0.1'; CREATE USER `root`(a)`127.0.0.1` I've upgraded all MariaDB servers that were installed with MariaDB <= 10.4 to MariaDB 10.6. I would like to update these root users, that were created when installing on < 10.4, to use UNIX socket authentication too. If I run: ALTER USER 'root'@'localhost' IDENTIFIED VIA mysql_native_password USING 'invalid' OR unix_socket ... I have a user with the same create statement as on servers that were installed with >= MariaDB 10.4: MariaDB [(none)]> show create user 'root'@'localhost'; CREATE USER `root`@`localhost` IDENTIFIED VIA mysql_native_password USING 'invalid' OR unix_socket I have 3 questions regarding this: 1. Is the ALTER USER statement above the correct migration path, to update root users created when installing on < 10.4 to use UNIX socket authentication, like root users created when installing on >= 10.4? Am I forgetting anything? 2. I presume the 'root'@'::1' and 'root'@'127.0.0.1' users were created to support TCP connections when skip_name_resolve=1. If so, they are no longer needed when using a UNIX socket. Can I safely delete these users, after updating the 'root'@'localhost' user to use UNIX socket authentication? 3. Is there a plan to automatically remove the debian-sys-maint user on future major upgrades? It still exists on servers that were installed on < 10.4. The /etc/mysql/debian.cnf file is deprecated already, so this user should be unused. FYI: All MariaDB servers were installed from the MariaDB Debian repository. Thank you! William Edwards

2 1

[Maria-discuss] Retrieve authentication plugins for user
by William Edwards 13 Oct '22

13 Oct '22

Hi, When creating an account with multiple authentication plugins, in this case 'unix_socket' OR 'mysql_native_password', the mysql.user.plugin column is set to either one. How should I retrieve *all* used authentication plugins for a given user? Example: ``` MariaDB [(none)]> CREATE USER 'testing'@'localhost' IDENTIFIED VIA unix_socket OR mysql_native_password USING 'invalid'; Query OK, 0 rows affected (0.005 sec) MariaDB [(none)]> select user,host,password,authentication_string,plugin from mysql.user where User = 'testing'; +---------+-----------+----------+-----------------------+-----------------------+ | User | Host | Password | authentication_string | plugin | +---------+-----------+----------+-----------------------+-----------------------+ | testing | localhost | invalid | invalid | mysql_native_password | +---------+-----------+----------+-----------------------+-----------------------+ 1 row in set (0.003 sec) ``` William Edwards

2 1

[Maria-discuss] What is the right way to update based on a DB change?
by ngtech1ltd＠gmail.com 03 Oct '22

03 Oct '22

Hey Everybody, I have the next scenario which I am not sure about the right way for a solution. I have a radius server that authenticate clients from multiple WIFI Access Points. I have couple systems and they need to know the current client login identifier (MAC or IP Address). It is stored in the DB and the DB is being updated on every login. I can try to give a static IP for every user and it will resolve this issue but there is an overhead for this. So what I was thinking instead is to either run a query that will fetch the latest changes or use a trigger to update another table which in turn will be read by an external software every 1-5 seconds. I believe that the right solution is to use a trigger that will update another table with the details and on the other table I will have a Processed column that will be updated when the software finished processing the row. Then in turn every 24 hours I will run a DB cleanup cron. I will try later on to share the schema. Any advice is more than welcome. Thanks, Eliezer ---- Eliezer Croitoru NgTech, Tech Support Mobile: +972-5-28704261 Email: <mailto:ngtech1ltd@gmail.com> ngtech1ltd(a)gmail.com Web: <https://ngtech.co.il/> https://ngtech.co.il/ My-Tube: <https://tube.ngtech.co.il/> https://tube.ngtech.co.il/

3 3

[Maria-discuss] LevelDB and KV best performance
by ngtech1ltd＠gmail.com 23 Aug '22

23 Aug '22

Hey, I have been using BDB and LevelDB and other KV embedded DB as an improvement for SquidGuard. I have seen the next MDEV: https://jira.mariadb.org/browse/MDEV-3841 And was wondering what is the most recommended way to store a simple KV list in MaraiDB these days. Currently MariaDB works fine for me but when I am comparing the performance of BDB to MariaDB even if am iterating a full DB file 6 times to find out if 6 different Keys are present it seems like a simple embedded DB is faster then MariaDB. I am not stating a fact since I don’t have the metrics but this is what it seems like. The DB is mainly for READ so I was thinking about an option to use a master and READ ONLY slaves to speedup the DB. The DB contains about 80 million rows so it’s not that big since the only thing I need is the KEY to match a category. Currently I am using a simple InnoDB table and the buffers are maximized to the maximum that the machine can offer. Thanks, Eliezer ---- Eliezer Croitoru NgTech, Tech Support Mobile: +972-5-28704261 Email: <mailto:ngtech1ltd@gmail.com> ngtech1ltd(a)gmail.com Web: <https://ngtech.co.il/> https://ngtech.co.il/ My-Tube: <https://tube.ngtech.co.il/> https://tube.ngtech.co.il/

1 0

[Maria-discuss] Change case with unique constraint
by Keith Edmunds 22 Aug '22

22 Aug '22

I can't change the case of a column with a unique index, example below. MariaDB [test]> show columns in kae; +-------+---------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-------+---------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | name | varchar(2048) | NO | UNI | NULL | | +-------+---------------+------+-----+---------+----------------+ 2 rows in set (0.001 sec) MariaDB [test]> select * from kae; +----+------+ | id | name | +----+------+ | 1 | test | +----+------+ 1 row in set (0.001 sec) MariaDB [test]> update kae set name="Test" where id=1; ERROR 1062 (23000): Duplicate entry 'Test' for key 'unique_name' MariaDB [test]>

4 3

[Maria-discuss] "Rewind" type of mechanisms?
by Sam R. 19 Aug '22

19 Aug '22

Hi! I would like to know about following topic regarding MariaDB.We would like to run DB cluster with HA (high availability). -- E.g. with MaxScale. My Q:Does MariaDB support such mechanism which would be similar to pg_rewind? Reference: PostgreSQL supports such a rewind operation.Or, are there plans to support such regarding MariaDB? ( If such would be needed / useful. ) Rewind: "A typical scenario is to bring an old primary server back online after failover as a standby that follows the new primary." Target: robustness/stability of a DB cluster. Avoiding needs to manually fix DB cluster. Best Regards Sam

3 7

[Maria-discuss] mysql_upgrade and error 'Table rebuild required. Please do "ALTER TABLE `table1` FORCE" or dump/reload to fix it!'
by Karl Levik 18 Aug '22

18 Aug '22

Hello list, After upgrading a database from 10.5 to 10.6 I get messages like below for a couple of the tables when I run mysql_upgrade: error : Table rebuild required. Please do "ALTER TABLE `table1` FORCE" or dump/reload to fix it! But at the end of the output it says: Repairing tables `database1`.`table1` FIXED `database1`.`table2` FIXED .... and so on - it lists all the tables that it previously said I needed to rebuild as "fixed". So, does that mean I don't need to do anything, or should I still run the ALTER TABLE statements? It seems I can SELECT + DELETE from and INSERT into the tables without getting any errors, so presumably I don't have to worry? Regards, Karl

1 0

[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] Major upgrade instructions missing for Galera
by William Edwards 10 Aug '22

10 Aug '22

Hi, The documentation at https://mariadb.com/kb/en/upgrading-galera-cluster/ is missing major upgrade instructions > MariaDB 10.4. Someone else caught this as well: https://mariadb.com/kb/en/upgrading-from-104-to-105-galera-changes/ Is this intentional? -- With kind regards, William Edwards

3 6

[Maria-discuss] ibtmp1 for internal temporary tablespaces
by William Edwards 09 Aug '22

09 Aug '22

Hi, User-created temporary tables are stored in ibtmp1. Are internal temporary tablespaces (those created by MariaDB while executing queries) too? I am unable to find the answer in the documentation[1]. Context: I'd like to store ibtmp1 in a different path using innodb_temp_data_file_path, but ONLY for user-created temporary tables. William Edwards [1]: https://mariadb.com/kb/en/innodb-temporary-tablespaces/ -- With kind regards, William Edwards

2 1

[Maria-discuss] Some questions about mariadb-dump and mariabackup
by jkmdb＠w3.org 02 Aug '22

02 Aug '22

Hi! Sorry to bother you about this but I haven't found the answers in the doc. ** mariadb-dump Could you tell me what is the difference of calling mariadb-dump on innodb tables using --skip-lock-tables --single-transaction? >From what I read these seem to be time / performace optimizations for doing innodb tables dumps but if we omit them, we would get the same data dumped, even it takes longer. Could you confirm this? ** mariabackup We have a setup that stores the binary logs under /var/log/mysql (set up with the log_bin configuration option) and the databases themselves under /var/lib/mysql Suppose I call mariabackup to make a backup of the database as follows (some options obmitted): mariabackup --backup --target-dir=my_backup_dir Could you tell me if calling mariabackup --prepare --target-dir=my_backup_dir needs access to the binary logs stored under /var/log/mysql or if mariabackup made a copy of all that it needs in my_backup_dir? ** mariabackup and incremental backups This is basically the same question as the above. If i'm making incremental backups as follows (some options obmitted): mariabackup --backup \ --target-dir=my_backup_dir/inc1 --incremental-basedir=full_backup_dir When I do the prepare for the incremental backups, does mariabackup need access to the /var/log/mysql bin logs or do the full + each incremental backup dirs has all the info needed to do the prepare? mariabackup --prepare \ --target-dir=my_backup_dir/inc1 --incremental-basedir=full_backup_dir Many thanks in advance! --josé

3 2

[Maria-discuss] MariaDB server horribly slow on start
by Cédric Counotte 01 Aug '22

01 Aug '22

Hello all. I hope I'm at the right place to ask this question. I opened a bug here: https://jira.mariadb.org/browse/MDEV-28969, however I was told to use this mailing list. We have 4 MariaDB servers in a Galera Cluster and it happens that a server has to be restarted (be it for a crash which I have to open a bug for) or maintenance. When that happens, the restarted server is causing huge slow down on the whole cluster, and it lasts for 10 to 30 minutes at the very least! And by huge, I mean huge, we end up with 500 to 800 pending queries on all servers as you can see on attached screenshots I've attached the configuration of any server for reference in case this is the source of the issue. Any way to solve this would be greatly appreciated. Regards, 3C.

8 45

[Maria-discuss] Looking for advice where to start looking at a slow query case
by ngtech1ltd＠gmail.com 26 Jul '22

26 Jul '22

Hey, I have tried to run a local service which claims to be a YouTube alike which is named AVideo(used to be PHPTube). I loaded the service with 220k+ videos from YouTube and have used MariaDB as the DB backend. The service moved slowly as the size of the videos DB growed from 100k to 150k. I got a recommendation from the developer to use MySQL which didn’t made any sense to me. I tracked the issue to the SQL queries that the service runs. Currently I am upgrading my local servers so the DB cannot be downloaded for testing however I have seen a very interesting thing. I will first put the query here: ```sql SELECT u.*, v.*, c.iconClass, c.name as category, c.clean_name as clean_category,c.description as category_description, v.created as videoCreation, v.modified as videoModified FROM videos as v LEFT JOIN categories c ON categories_id = c.id LEFT JOIN users u ON v.users_id = u.id WHERE 2=2 AND u.status = 'a' AND v.status IN ('a','k','f') ORDER BY likes DESC LIMIT 36, 12; ``` The ANALYZE FORMAT=JSON for that query is: ```json { "query_block": { "select_id": 1, "r_loops": 1, "r_total_time_ms": 9643.807074, "filesort": { "sort_key": "v.likes desc", "r_loops": 1, "r_total_time_ms": 756.223544, "r_limit": 48, "r_used_priority_queue": true, "r_output_rows": 49, "r_sort_mode": "sort_key,rowid", "temporary_table": { "table": { "table_name": "u", "access_type": "ref", "possible_keys": ["PRIMARY", "users_status_IDX"], "key": "users_status_IDX", "key_length": "1", "used_key_parts": ["status"], "ref": ["const"], "r_loops": 1, "rows": 1, "r_rows": 1, "r_table_time_ms": 0.034852389, "r_other_time_ms": 0.020715696, "filtered": 100, "r_filtered": 100, "index_condition": "u.`status` = 'a'" }, "table": { "table_name": "v", "access_type": "ref", "possible_keys": [ "fk_videos_users_idx", "video_status_idx", "videos_status_index" ], "key": "fk_videos_users_idx", "key_length": "4", "used_key_parts": ["users_id"], "ref": ["AVideo.u.id"], "r_loops": 1, "rows": 391299, "r_rows": 990067, "r_table_time_ms": 2691.791742, "r_other_time_ms": 6129.887127, "filtered": 50.00025558, "r_filtered": 100, "attached_condition": "v.`status` in ('a','k','f')" }, "table": { "table_name": "c", "access_type": "eq_ref", "possible_keys": ["PRIMARY"], "key": "PRIMARY", "key_length": "4", "used_key_parts": ["id"], "ref": ["AVideo.v.categories_id"], "r_loops": 990067, "rows": 1, "r_rows": 1, "r_table_time_ms": 0.00546745, "r_other_time_ms": 0.569425897, "filtered": 100, "r_filtered": 100 } } } } } ``` While for the next: ```sql SELECT * FROM (SELECT u.id as uid , u.user as uuser , u.name as uname , u.email as uemail , u.password as upassword , u.created as ucreated , u.modified as umodified , u.isAdmin as uisAdmin , u.status as ustatus , u.photoURL as uphotoURL , u.lastLogin as ulastLogin , u.recoverPass as urecoverPass , u.backgroundURL as ubackgroundURL , u.canStream as ucanStream , u.canUpload as ucanUpload , u.canCreateMeet as ucanCreateMeet , u.canViewChart as ucanViewChart , u.about as uabout , u.channelName as uchannelName , u.emailVerified as uemailVerified , u.analyticsCode as uanalyticsCode , u.externalOptions as uexternalOptions , u.first_name as ufirst_name , u.last_name as ulast_name , u.address as uaddress , u.zip_code as uzip_code , u.country as ucountry , u.region as uregion , u.city as ucity , u.donationLink as udonationLink , u.extra_info as uextra_info , u.phone as uphone , u.is_company as uis_company , v.*, c.iconClass, c.name as category, c.clean_name as clean_category,c.description as category_description, v.created as videoCreation, v.modified as videoModified FROM videos as v LEFT JOIN categories c ON categories_id = c.id LEFT JOIN users u ON v.users_id = u.id WHERE 2=2 AND v.status IN ('a','k','f') ORDER BY likes DESC ) a WHERE a.ustatus IN ('a') LIMIT 1000, 900; ``` The ANALYZE FORMAT=JSON is the next: ```json { "query_block": { "select_id": 1, "r_loops": 1, "r_total_time_ms": 8.047324959, "table": { "table_name": "u", "access_type": "ref", "possible_keys": ["PRIMARY", "users_status_IDX"], "key": "users_status_IDX", "key_length": "1", "used_key_parts": ["status"], "ref": ["const"], "r_loops": 1, "rows": 1, "r_rows": 1, "r_table_time_ms": 0.045761237, "r_other_time_ms": 0.0201165, "filtered": 100, "r_filtered": 100, "index_condition": "u.`status` = 'a'" }, "table": { "table_name": "v", "access_type": "ref", "possible_keys": [ "fk_videos_users_idx", "video_status_idx", "videos_status_index" ], "key": "fk_videos_users_idx", "key_length": "4", "used_key_parts": ["users_id"], "ref": ["AVideo.u.id"], "r_loops": 1, "rows": 391299, "r_rows": 1900, "r_table_time_ms": 6.939235389, "r_other_time_ms": 1.010973728, "filtered": 50.00025558, "r_filtered": 100, "attached_condition": "v.`status` in ('a','k','f')" }, "table": { "table_name": "c", "access_type": "eq_ref", "possible_keys": ["PRIMARY"], "key": "PRIMARY", "key_length": "4", "used_key_parts": ["id"], "ref": ["AVideo.v.categories_id"], "r_loops": 1900, "rows": 1, "r_rows": 1, "r_table_time_ms": 0.007669714, "r_other_time_ms": 0.001959112, "filtered": 100, "r_filtered": 100 } } } ``` And what I am trying to understand is, what's the difference? Why would the same exact query will result with this issue? Just to notice that the next query will not run at all due to fields naming conflict between u and v: ```sql SELECT * FROM (SELECT u.* , v.*, c.iconClass, c.name as category, c.clean_name as clean_category,c.description as category_description, v.created as videoCreation, v.modified as videoModified FROM videos as v LEFT JOIN categories c ON categories_id = c.id LEFT JOIN users u ON v.users_id = u.id WHERE 2=2 AND v.status IN ('a','k','f') ORDER BY likes DESC ) a WHERE a.ustatus IN ('a') LIMIT 1000, 900; ``` I am not new to the DB world that much but it's the first time I am getting my hands dirty about such an issue. I will share the full DB later on today so it could be used as a learning material. Also, are there any big public databases that can be used for learning and testing purposes? Thanks, Eliezer ---- Eliezer Croitoru NgTech, Tech Support Mobile: +972-5-28704261 Email: ngtech1ltd(a)gmail.com Web: https://ngtech.co.il/ My-Tube: https://tube.ngtech.co.il/

3 10

[Maria-discuss] mariadb-connector-cpp and multiple threads
by jason＠youtorque.com 25 Jul '22

25 Jul '22

Using the [ MariaDB C++ Connector ]( https://github.com/mariadb-corporation/mariadb-connector-cpp ) on ubuntu 20.04, and gcc compiler. During load test of a webserver application it was discovered that anytime there was more than a single concurrent connection the server would crash. This was narrowed down to the connect member of the mariadb driver. The errors that were being reported were always one of the following two: terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_M_construct null not validAborted (core dumped)terminate called after throwing an instance of 'std::invalid_argument' what(): stoiAborted (core dumped) As it wouldn't be feasible to post the source of the server, I have reproduced a minimal working example that uses only standard library and mariadb/conncpp.hpp: ``` #include <mariadb/conncpp.hpp>#include <iostream>#include <thread>#include <string>sql::Driver* driver = sql::mariadb::get_driver_instance();sql::SQLString connectionUrl = "jdbc:mariadb://localhost:3306/the_database_name";sql::Properties properties = {{"user", "the_username"}, {"password", "the_password"}};int main(){ // simulate 2 concurrent connections each making 500 requests std::vector<std::function<void()>> t1cbs; std::vector<std::function<void()>> t2cbs; for(int i = 0; i < 500; i++) // if does not fail for you at 500 up the number until it does { t1cbs.push_back([&]{ std::unique_ptr<sql::Connection> conn(driver->connect(connectionUrl, properties)); std::cout << "t1:" << conn->getHostname().c_str() << std::endl; }); // comment out this block to keep the second thread from executing, and you will see // that no errors occur t2cbs.push_back([&]{ std::unique_ptr<sql::Connection> conn(driver->connect(connectionUrl, properties)); std::cout << "t2:" << conn->getHostname().c_str() << std::endl; }); } std::thread t1([&]{ for(auto& cb : t1cbs) cb(); }); std::thread t2([&]{ for(auto& cb : t2cbs) cb(); }); t1.join(); t2.join(); return 0;} ``` I'm guessing the issue is on my end as I've just started working with this particular library and have probably missed or misunderstood something. Would someone be able to point me in the right direction as far as how I might go about creating database connections from within separate threads?

2 3

Re: [Maria-discuss] mysql_upgrade fails
by Majed Zouhairy 21 Jul '22

21 Jul '22

on centos 8, upgrade form mraidb 10.3 to 10.6 fails with: sudo mysql_upgrade -u root -p Enter password: Major version upgrade detected from 10.3.17-MariaDB to 10.6.8-MariaDB. Check required! Phase 1/7: Checking and upgrading mysql database Processing databases mysql mysql.column_stats OK mysql.columns_priv OK mysql.db OK mysql.event OK mysql.func OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK mysql.host OK mysql.index_stats OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.roles_mapping OK mysql.servers OK mysql.table_stats OK mysql.tables_priv OK mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK Phase 2/7: Installing used storage engines... Skipped Phase 3/7: Fixing views Phase 4/7: Running 'mysql_fix_privilege_tables' ERROR 1005 (HY000) at line 694: Can't create table `mysql`.`innodb_table_stats` (errno: 184 "Tablespace already exists") ERROR 1005 (HY000) at line 698: Can't create table `mysql`.`innodb_index_stats` (errno: 184 "Tablespace already exists") ERROR 1005 (HY000) at line 702: Can't create table `mysql`.`transaction_registry` (errno: 184 "Tablespace already exists") ERROR 1005 (HY000) at line 774: Can't create table `mysql`.`gtid_slave_pos` (errno: 184 "Tablespace already exists") FATAL ERROR: Upgrade failed ________________________________ From: Vicențiu Ciorbaru <cvicentiu(a)gmail.com> Sent: Wednesday, April 21, 2021 3:51 PM To: Majed Zouhairy <majedzouhairy(a)hotmail.com> Cc: maria-discuss(a)lists.launchpad.net <maria-discuss(a)lists.launchpad.net> Subject: Re: [Maria-discuss] mysql_upgrade fails Hi Majed, What MariaDB version is this? What is the previous version and what is the current version you are upgrading to? Is this from a linux distro, or where did you get the MariaDB binary from? If it's a distro, which one? Vicențiu On Wed, 21 Apr 2021 at 15:31, Majed Zouhairy <majedzouhairy(a)hotmail.com<mailto:majedzouhairy@hotmail.com>> wrote: in last time's upgrade and today i got: sudo mysql_upgrade -u root -p Enter password: Phase 1/7: Checking and upgrading mysql database Processing databases mysql mysql.column_stats OK mysql.columns_priv OK mysql.db OK mysql.event OK mysql.func OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK mysql.host OK mysql.index_stats OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.roles_mapping OK mysql.servers OK mysql.table_stats OK mysql.tables_priv OK mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK Phase 2/7: Installing used storage engines... Skipped Phase 3/7: Fixing views Phase 4/7: Running 'mysql_fix_privilege_tables' ERROR 1813 (HY000) at line 77: Tablespace for table '`mysql`.`innodb_table_stats`' exists. Please DISCARD the tablespace before IMPORT ERROR 1813 (HY000) at line 81: Tablespace for table '`mysql`.`innodb_index_stats`' exists. Please DISCARD the tablespace before IMPORT ERROR 1813 (HY000) at line 85: Tablespace for table '`mysql`.`transaction_registry`' exists. Please DISCARD the tablespace before IMPORT ERROR 1813 (HY000) at line 153: Tablespace for table '`mysql`.`gtid_slave_pos`' exists. Please DISCARD the tablespace before IMPORT ERROR 1146 (42S02) at line 642: Table 'mysql.innodb_index_stats' doesn't exist ERROR 1243 (HY000) at line 643: Unknown prepared statement handler (stmt) given to EXECUTE ERROR 1146 (42S02) at line 645: Table 'mysql.innodb_table_stats' doesn't exist ERROR 1243 (HY000) at line 646: Unknown prepared statement handler (stmt) given to EXECUTE ERROR 1146 (42S02) at line 650: Table 'mysql.innodb_index_stats' doesn't exist ERROR 1146 (42S02) at line 654: Table 'mysql.innodb_table_stats' doesn't exist ERROR 1146 (42S02) at line 657: Table 'mysql.innodb_table_stats' doesn't exist FATAL ERROR: Upgrade failed what to do? _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net<mailto:maria-discuss@lists.launchpad.net> Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

3 8

[Maria-discuss] Speeding up MyRocks engine
by Jan Křístek 24 Jun '22

24 Jun '22

Hello, I have already given up on MyRocks but could someone give some hint to take back my decision?. I have a setup with a heavy insert load with potentially long records (up to a kilobyte or two). I cannot get more than about 300-400 inserts per second with MyRocks. With the Aria engine, it's reaching up to 1900 inserts/sec with the same setup. The only config changes for MyRocks are: rocksdb-override-cf-options='cf1={compression=kLZ4Compression;bottommost_compression=kLZ4Compression;}' rocksdb_allow_concurrent_memtable_write = ON rocksdb_default_cf_options=block_based_table_factory={cache_index_and_filter_blocks=1;filter_policy=bloomfilter:10:false;whole_key_filtering=1};level_compaction_dynamic_level_bytes=true;optimize_filters_for_hits=true;compaction_pri=kMinOverlappingRatio;compression=kLZ4Compression plugin-load-add=ha_rocksdb.so Both MyRocks and Aria are the same hardware, the same setup SSD with software Raid0 and LVM. With Aria I have switched on aria_group_commit to "soft" with 500 ms delay, as I understand, I might lose some data if the server is hard killed or crashes. I am willing to take the risk unless s/o suggests a major speedup for the MyRocks. I have switched TRANSACTIONAL=1 for the table. The table has partitions on both Aria and MyRocks. Thank you for any help in advance, Jan

1 0

[Maria-discuss] Change delimiter with server_audit plugin
by Philippe Maladjian 22 Jun '22

22 Jun '22

Hi there, In order to monitor a database and especially the requests that could be in error, I activated the server_audit plugin. Plugin setup: show global VARIABLES like '%server_audit%'; +-------------------------------+---------------------------------+ | Variable_name | Value | +-------------------------------+---------------------------------+ | server_audit_events | QUERY | | server_audit_excl_users | user | | server_audit_file_path | /var/log/mysql/server_audti.log | | server_audit_file_rotate_now | OFF | | server_audit_file_rotate_size | 1000000 | | server_audit_file_rotations | 9 | | server_audit_incl_users | user | | server_audit_logging | ON | | server_audit_mode | 0 | | server_audit_output_type | file | | server_audit_query_log_limit | 1024 | | server_audit_syslog_facility | LOG_USER | | server_audit_syslog_ident | mysql-server_auditing | | server_audit_syslog_info | | | server_audit_syslog_priority | LOG_ERR | +-------------------------------+---------------------------------+ My problem is that the separator between each value is the comma and bad luck it's the same separator as in the query. Example of a line: 20220622 08:35:03,sserver,user,localhost,14858,7002875,QUERY,database,'UPDATE sorderq SET `odlqty` = "6", `soqsta` = "3", `sdhnum` = "LIVHIL22062", `sddlin` = 24000 WHERE `sohnum` = "NORHIL220601" AND `soplin` = 24000 AND `soqseq` = 24000',0 [...] 20220622 08:35:03,server,user,localhost,14858,7002878,QUERY,database,'INSERT INTO sdeliveryd(`sdhnum`, `itmref`, `sddlin`, `netprinot`, `qty`, `rtnqty`, `tsicod0`, `tsicod1`, `tsicod2`, `tsicod3`, `tsicod4`, `rep1`) VALUES("LIVHIL22061", "1-11325", 26000, 0.0, "12", "0", "STA", "05", " ", " ", " ", "093")',0 It is the last field that interests me because it is the return code of the request. Now if I want to automate the error processing (last field <> 0) I simply cannot because due to the identical separator between the fields of the request and the fields of the log line, the number of columns varies and the return code never has the same position. Is it possible to change the field separator in the plugin? Thanks in advance

1 0

[Maria-discuss] debug.csr error?
by Dave Pawson 19 Jun '22

19 Jun '22

Using create table. error shown > python createRItbl.py Debug.csr Traceback (most recent call last): File "/home/dpawson/Dropbox/2022/sibc/software/mariadb/createRItbl.py", line 82, in <module> showcsr(csr) File "/home/dpawson/Dropbox/2022/sibc/software/mariadb/createRItbl.py", line 40, in showcsr for item in csr: File "/home/dpawson/.local/lib/python3.10/site-packages/mysql/connector/cursor_cext.py", line 718, in fetchone return self._fetch_row() File "/home/dpawson/.local/lib/python3.10/site-packages/mysql/connector/cursor_cext.py", line 689, in _fetch_row row = self._rows[self._next_row] TypeError: 'NoneType' object is not subscriptable Called from Python. Table= f"CREATE TABLE IF NOT EXISTS rinkincome (\ matchdate DATE ,\ session ENUM('rollup','league','club match') ,\ code ENUM {costcodes} ,\ cashOrCard ENUM('card','cash'),\ amount DECIMAL(5,2) );" where costcodes=('a','b') form. # print Table out to check syntax #print(Table) #sys.exit(0) csr.execute(Table) showcsr(csr) Nothing shown to indicate which list / structure I'm trying to iterate over? Any suggestions to chase down the fault please. Pretty new to mariadb. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.

1 0

[Maria-discuss] Incorrect Documentation: Replicating JSON from MySQL to MariaDB
by Gordan Bobic 29 May '22

29 May '22

On this page: https://mariadb.com/kb/en/json-data-type/ it states: If you must use row-based replication and cannot change the MySQL master from JSON to TEXT, you can try to introduce an intermediate MySQL slave and change the column type from JSON to TEXT on it. Then you replicate from this intermediate slave to MariaDB. I can confirm that this does not work with MySQL 5.7. If you have a 5.7 master and you replicate to 5.7 slave, and you convert the slave's json columns to longtext, replication fails with this error: "Column X of table 'dbname.tablename' cannot be converted from type 'json' to type 'longtext'" Using longblob doesn't work either. So it seems there is currently no viable solution for replicating anything that involves JSON columns from MySQL to MariaDB.

2 2

[Maria-discuss] Custom Galera SST Method Documentation
by Gordan Bobic 27 May '22

27 May '22

Hi, I vaguely remember reading something years ago about implementing a custom SST method, but I cannot seem to find any documentation for it now. Is there any documentation on the interfaces that scripts need to implement and how to hook up said scripts into the config files?

2 2

[Maria-discuss] dpkg: mariadb-client-10.x: dependency problems, but removing anyway as you requested
by William Edwards 25 May '22

25 May '22

Hi, Using the official MariaDB repos, since MariaDB 10.4, mariadb-client-10.x is removed, then installed on 'apt upgrade': ``` Unpacking libmariadb3:amd64 (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... dpkg: mariadb-client-10.7: dependency problems, but removing anyway as you requested: mariadb-server-10.7 depends on mariadb-client-10.7 (>= 1:10.7.3+maria~buster). mariadb-client depends on mariadb-client-10.7 (>= 1:10.7.4+maria~buster). (Reading database ... 87804 files and directories currently installed.) Removing mariadb-client-10.7 (1:10.7.3+maria~buster) ... Setting up mysql-common (1:10.7.4+maria~buster) ... Setting up mariadb-common (1:10.7.4+maria~buster) ... (Reading database ... 87703 files and directories currently installed.) Preparing to unpack .../00-mariadb-server-10.7_1%3a10.7.4+maria~buster_amd64.deb ... /var/lib/mysql: found previous version 10.7 Unpacking mariadb-server-10.7 (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Preparing to unpack .../01-mariadb-server-core-10.7_1%3a10.7.4+maria~buster_amd64.deb ... Unpacking mariadb-server-core-10.7 (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Preparing to unpack .../02-mariadb-client-core-10.7_1%3a10.7.4+maria~buster_amd64.deb ... Unpacking mariadb-client-core-10.7 (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Selecting previously unselected package mariadb-client-10.7. Preparing to unpack .../03-mariadb-client-10.7_1%3a10.7.4+maria~buster_amd64.deb ... Unpacking mariadb-client-10.7 (1:10.7.4+maria~buster) ... ``` This does not seem to be a problem, but I'd like to understand what changed between 10.3 and 10.4 that causes this. Policy output and full 'apt upgrade' transaction log: ``` root@http-msh01:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: filebeat libavcodec58 libavfilter7 libavformat58 libavutil56 libldap-2.4-2 libldap-common libmariadb-dev libmariadb-dev-compat libmariadb3 libpostproc55 libpq5 libssl-dev libssl1.1 libswresample3 libswscale5 libxml2 mariadb-client mariadb-client-10.7 mariadb-client-core-10.7 mariadb-common mariadb-server mariadb-server-10.7 mariadb-server-core-10.7 mysql-common nodejs openjdk-11-jre openjdk-11-jre-headless openssl php8.1 php8.1-bcmath php8.1-cli php8.1-common php8.1-curl php8.1-dev php8.1-fpm php8.1-gd php8.1-imap php8.1-intl php8.1-mbstring php8.1-mysql php8.1-opcache php8.1-readline php8.1-soap php8.1-sqlite3 php8.1-xml php8.1-zip sensu-go-agent 55 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 142 MB of archives. After this operation, 10.3 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://security.debian.org/debian-security buster/updates/main amd64 libssl-dev amd64 1.1.1n-0+deb10u2 [1,807 kB] Get:9 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 mysql-common all 1:10.7.4+maria~buster [2,880 B] Get:10 http://security.debian.org/debian-security buster/updates/main amd64 libssl1.1 amd64 1.1.1n-0+deb10u2 [1,551 kB] Get:11 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 mariadb-common all 1:10.7.4+maria~buster [4,052 B] Get:12 http://security.debian.org/debian-security buster/updates/main amd64 libldap-common all 2.4.47+dfsg-3+deb10u7 [90.1 kB] Get:13 http://security.debian.org/debian-security buster/updates/main amd64 libldap-2.4-2 amd64 2.4.47+dfsg-3+deb10u7 [224 kB] Get:14 https://artifacts.elastic.co/packages/7.x/apt stable/main amd64 filebeat amd64 7.17.4 [37.8 MB] Get:15 http://security.debian.org/debian-security buster/updates/main amd64 libavfilter7 amd64 7:4.1.9-0+deb10u1 [1,053 kB] Get:16 https://packages.sury.org/php buster/main amd64 libxml2 amd64 2.9.14+dfsg-0+0~20220524.12+debian10~1.gbpc5dc45 [701 kB] Get:17 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 mariadb-server all 1:10.7.4+maria~buster [2,832 B] Get:18 http://security.debian.org/debian-security buster/updates/main amd64 libswscale5 amd64 7:4.1.9-0+deb10u1 [209 kB] Get:19 http://security.debian.org/debian-security buster/updates/main amd64 libavformat58 amd64 7:4.1.9-0+deb10u1 [1,019 kB] Get:20 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 mariadb-client all 1:10.7.4+maria~buster [2,704 B] Get:21 http://security.debian.org/debian-security buster/updates/main amd64 libavcodec58 amd64 7:4.1.9-0+deb10u1 [4,810 kB] Get:22 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 libmariadb-dev amd64 1:10.7.4+maria~buster [158 kB] Get:23 https://packages.sury.org/php buster/main amd64 php8.1-bcmath amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [15.4 kB] Get:24 https://packages.sury.org/php buster/main amd64 php8.1-zip amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [24.2 kB] Get:25 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 libmariadb-dev-compat amd64 1:10.7.4+maria~buster [3,084 B] Get:26 https://packages.sury.org/php buster/main amd64 php8.1-xml amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [107 kB] Get:27 https://packages.sury.org/php buster/main amd64 php8.1-sqlite3 amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [29.3 kB] Get:28 https://packages.sury.org/php buster/main amd64 php8.1-soap amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [120 kB] Get:29 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 libmariadb3 amd64 1:10.7.4+maria~buster [148 kB] Get:30 https://packages.sury.org/php buster/main amd64 php8.1-readline amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [12.6 kB] Get:31 https://packages.sury.org/php buster/main amd64 php8.1-opcache amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [332 kB] Get:32 https://packages.sury.org/php buster/main amd64 php8.1-mysql amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [116 kB] Get:33 https://packages.sury.org/php buster/main amd64 php8.1-mbstring amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [396 kB] Get:34 https://packages.sury.org/php buster/main amd64 php8.1-intl amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [127 kB] Get:35 https://packages.sury.org/php buster/main amd64 php8.1-imap amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [32.6 kB] Get:36 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 mariadb-client-core-10.7 amd64 1:10.7.4+maria~buster [832 kB] Get:37 https://packages.sury.org/php buster/main amd64 php8.1-gd amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [28.5 kB] Get:38 https://packages.sury.org/php buster/main amd64 php8.1-dev amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [488 kB] Get:39 https://packages.sury.org/php buster/main amd64 php8.1-curl amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [34.4 kB] Get:40 https://packages.sury.org/php buster/main amd64 php8.1-fpm amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [1,672 kB] Get:41 http://security.debian.org/debian-security buster/updates/main amd64 libswresample3 amd64 7:4.1.9-0+deb10u1 [112 kB] Get:42 http://security.debian.org/debian-security buster/updates/main amd64 libpostproc55 amd64 7:4.1.9-0+deb10u1 [108 kB] Get:43 http://security.debian.org/debian-security buster/updates/main amd64 libavutil56 amd64 7:4.1.9-0+deb10u1 [244 kB] Get:44 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 mariadb-server-10.7 amd64 1:10.7.4+maria~buster [3,461 kB] Get:45 https://packages.sury.org/php buster/main amd64 php8.1-cli amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [1,662 kB] Get:46 http://security.debian.org/debian-security buster/updates/main amd64 libpq5 amd64 11.16-0+deb10u1 [172 kB] Get:47 https://packages.sury.org/php buster/main amd64 php8.1-common amd64 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [660 kB] Get:48 http://security.debian.org/debian-security buster/updates/main amd64 openjdk-11-jre amd64 11.0.15+10-1~deb10u1 [174 kB] Get:49 https://packages.sury.org/php buster/main amd64 php8.1 all 8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1 [24.7 kB] Get:50 http://security.debian.org/debian-security buster/updates/main amd64 openjdk-11-jre-headless amd64 11.0.15+10-1~deb10u1 [37.2 MB] Get:51 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 mariadb-client-10.7 amd64 1:10.7.4+maria~buster [2,411 kB] Get:52 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 mariadb-server-core-10.7 amd64 1:10.7.4+maria~buster [7,153 kB] Get:53 https://packagecloud.io/sensu/stable/debian buster/main amd64 sensu-go-agent amd64 6.7.2-6283 [6,975 kB] Get:54 http://security.debian.org/debian-security buster/updates/main amd64 openssl amd64 1.1.1n-0+deb10u2 [855 kB] Get:55 https://deb.nodesource.com/node_16.x buster/main amd64 nodejs amd64 16.15.0-deb-1nodesource1 [26.4 MB] Fetched 142 MB in 6s (24.2 MB/s) Reading changelogs... Done Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 87804 files and directories currently installed.) Preparing to unpack .../0-mysql-common_1%3a10.7.4+maria~buster_all.deb ... Unpacking mysql-common (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Preparing to unpack .../1-mariadb-common_1%3a10.7.4+maria~buster_all.deb ... Unpacking mariadb-common (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Preparing to unpack .../2-mariadb-server_1%3a10.7.4+maria~buster_all.deb ... Unpacking mariadb-server (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Preparing to unpack .../3-mariadb-client_1%3a10.7.4+maria~buster_all.deb ... Unpacking mariadb-client (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Preparing to unpack .../4-libmariadb-dev_1%3a10.7.4+maria~buster_amd64.deb ... Unpacking libmariadb-dev (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Preparing to unpack .../5-libmariadb-dev-compat_1%3a10.7.4+maria~buster_amd64.deb ... Unpacking libmariadb-dev-compat:amd64 (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Preparing to unpack .../6-libssl-dev_1.1.1n-0+deb10u2_amd64.deb ... Unpacking libssl-dev:amd64 (1.1.1n-0+deb10u2) over (1.1.1n-0+deb10u1) ... Preparing to unpack .../7-libssl1.1_1.1.1n-0+deb10u2_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1n-0+deb10u2) over (1.1.1n-0+deb10u1) ... Preparing to unpack .../8-libmariadb3_1%3a10.7.4+maria~buster_amd64.deb ... Unpacking libmariadb3:amd64 (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... dpkg: mariadb-client-10.7: dependency problems, but removing anyway as you requested: mariadb-server-10.7 depends on mariadb-client-10.7 (>= 1:10.7.3+maria~buster). mariadb-client depends on mariadb-client-10.7 (>= 1:10.7.4+maria~buster). (Reading database ... 87804 files and directories currently installed.) Removing mariadb-client-10.7 (1:10.7.3+maria~buster) ... Setting up mysql-common (1:10.7.4+maria~buster) ... Setting up mariadb-common (1:10.7.4+maria~buster) ... (Reading database ... 87703 files and directories currently installed.) Preparing to unpack .../00-mariadb-server-10.7_1%3a10.7.4+maria~buster_amd64.deb ... /var/lib/mysql: found previous version 10.7 Unpacking mariadb-server-10.7 (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Preparing to unpack .../01-mariadb-server-core-10.7_1%3a10.7.4+maria~buster_amd64.deb ... Unpacking mariadb-server-core-10.7 (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Preparing to unpack .../02-mariadb-client-core-10.7_1%3a10.7.4+maria~buster_amd64.deb ... Unpacking mariadb-client-core-10.7 (1:10.7.4+maria~buster) over (1:10.7.3+maria~buster) ... Selecting previously unselected package mariadb-client-10.7. Preparing to unpack .../03-mariadb-client-10.7_1%3a10.7.4+maria~buster_amd64.deb ... Unpacking mariadb-client-10.7 (1:10.7.4+maria~buster) ... Preparing to unpack .../04-libldap-common_2.4.47+dfsg-3+deb10u7_all.deb ... Unpacking libldap-common (2.4.47+dfsg-3+deb10u7) over (2.4.47+dfsg-3+deb10u6) ... Preparing to unpack .../05-libldap-2.4-2_2.4.47+dfsg-3+deb10u7_amd64.deb ... Unpacking libldap-2.4-2:amd64 (2.4.47+dfsg-3+deb10u7) over (2.4.47+dfsg-3+deb10u6) ... Preparing to unpack .../06-libavfilter7_7%3a4.1.9-0+deb10u1_amd64.deb ... Unpacking libavfilter7:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ... Preparing to unpack .../07-libswscale5_7%3a4.1.9-0+deb10u1_amd64.deb ... Unpacking libswscale5:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ... Preparing to unpack .../08-libavformat58_7%3a4.1.9-0+deb10u1_amd64.deb ... Unpacking libavformat58:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ... Preparing to unpack .../09-libavcodec58_7%3a4.1.9-0+deb10u1_amd64.deb ... Unpacking libavcodec58:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ... Preparing to unpack .../10-libswresample3_7%3a4.1.9-0+deb10u1_amd64.deb ... Unpacking libswresample3:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ... Preparing to unpack .../11-libpostproc55_7%3a4.1.9-0+deb10u1_amd64.deb ... Unpacking libpostproc55:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ... Preparing to unpack .../12-libavutil56_7%3a4.1.9-0+deb10u1_amd64.deb ... Unpacking libavutil56:amd64 (7:4.1.9-0+deb10u1) over (7:4.1.8-0+deb10u1) ... Preparing to unpack .../13-libxml2_2.9.14+dfsg-0+0~20220524.12+debian10~1.gbpc5dc45_amd64.deb ... Unpacking libxml2:amd64 (2.9.14+dfsg-0+0~20220524.12+debian10~1.gbpc5dc45) over (2.9.13+dfsg-0+0~20220410.11+debian10~1.gbp692312) ... Preparing to unpack .../14-libpq5_11.16-0+deb10u1_amd64.deb ... Unpacking libpq5:amd64 (11.16-0+deb10u1) over (11.14-0+deb10u1) ... Preparing to unpack .../15-nodejs_16.15.0-deb-1nodesource1_amd64.deb ... Unpacking nodejs (16.15.0-deb-1nodesource1) over (16.14.2-deb-1nodesource1) ... Preparing to unpack .../16-openjdk-11-jre_11.0.15+10-1~deb10u1_amd64.deb ... Unpacking openjdk-11-jre:amd64 (11.0.15+10-1~deb10u1) over (11.0.14+9-1~deb10u1) ... Preparing to unpack .../17-openjdk-11-jre-headless_11.0.15+10-1~deb10u1_amd64.deb ... Unpacking openjdk-11-jre-headless:amd64 (11.0.15+10-1~deb10u1) over (11.0.14+9-1~deb10u1) ... Preparing to unpack .../18-openssl_1.1.1n-0+deb10u2_amd64.deb ... Unpacking openssl (1.1.1n-0+deb10u2) over (1.1.1n-0+deb10u1) ... Preparing to unpack .../19-php8.1-bcmath_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-bcmath (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../20-php8.1-zip_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-zip (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../21-php8.1-xml_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-xml (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../22-php8.1-sqlite3_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-sqlite3 (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../23-php8.1-soap_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-soap (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../24-php8.1-readline_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-readline (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../25-php8.1-opcache_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-opcache (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../26-php8.1-mysql_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-mysql (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../27-php8.1-mbstring_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-mbstring (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../28-php8.1-intl_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-intl (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../29-php8.1-imap_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-imap (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../30-php8.1-gd_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-gd (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../31-php8.1-dev_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-dev (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../32-php8.1-curl_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-curl (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../33-php8.1-fpm_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-fpm (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../34-php8.1-cli_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-cli (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../35-php8.1-common_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_amd64.deb ... Unpacking php8.1-common (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../36-php8.1_8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1_all.deb ... Unpacking php8.1 (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) over (8.1.5-1+0~20220422.16+debian10~1.gbpfcaf04) ... Preparing to unpack .../44-sensu-go-agent_6.7.2-6283_amd64.deb ... Unpacking sensu-go-agent (6.7.2-6283) over (6.7.0-6196) ... Preparing to unpack .../45-filebeat_7.17.4_amd64.deb ... Unpacking filebeat (7.17.4) over (7.17.3) ... Setting up libssl1.1:amd64 (1.1.1n-0+deb10u2) ... Setting up openjdk-11-jre-headless:amd64 (11.0.15+10-1~deb10u1) ... Setting up openjdk-11-jre:amd64 (11.0.15+10-1~deb10u1) ... Setting up nodejs (16.15.0-deb-1nodesource1) ... Setting up libldap-common (2.4.47+dfsg-3+deb10u7) ... Setting up libavutil56:amd64 (7:4.1.9-0+deb10u1) ... Setting up libssl-dev:amd64 (1.1.1n-0+deb10u2) ... Setting up libpostproc55:amd64 (7:4.1.9-0+deb10u1) ... Setting up libmariadb3:amd64 (1:10.7.4+maria~buster) ... Setting up libmariadb-dev (1:10.7.4+maria~buster) ... Setting up sensu-go-agent (6.7.2-6283) ... Setting up libswscale5:amd64 (7:4.1.9-0+deb10u1) ... Setting up mariadb-server-core-10.7 (1:10.7.4+maria~buster) ... Setting up filebeat (7.17.4) ... Installing new version of config file /etc/filebeat/filebeat.reference.yml ... Configuration file '/etc/filebeat/filebeat.yml' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** filebeat.yml (Y/I/N/O/D/Z) [default=N] ? Installing new version of config file /etc/filebeat/modules.d/azure.yml.disabled ... Setting up openssl (1.1.1n-0+deb10u2) ... Setting up libxml2:amd64 (2.9.14+dfsg-0+0~20220524.12+debian10~1.gbpc5dc45) ... Setting up libmariadb-dev-compat:amd64 (1:10.7.4+maria~buster) ... Installing all pip dependencies Requirement already satisfied: pika==1.2.0 in /usr/local/lib/python3.7/dist-packages (1.2.0) Setting up php8.1-common (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up php8.1-imap (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up php8.1-gd (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up libldap-2.4-2:amd64 (2.4.47+dfsg-3+deb10u7) ... Setting up libswresample3:amd64 (7:4.1.9-0+deb10u1) ... Setting up php8.1-curl (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up php8.1-sqlite3 (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up php8.1-xml (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up php8.1-soap (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up mariadb-client-core-10.7 (1:10.7.4+maria~buster) ... Setting up php8.1-mysql (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up php8.1-zip (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up libavcodec58:amd64 (7:4.1.9-0+deb10u1) ... Setting up php8.1-readline (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up mariadb-client-10.7 (1:10.7.4+maria~buster) ... Setting up php8.1-opcache (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up php8.1-intl (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up php8.1-bcmath (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up mariadb-client (1:10.7.4+maria~buster) ... Setting up php8.1-mbstring (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up libavformat58:amd64 (7:4.1.9-0+deb10u1) ... Setting up libpq5:amd64 (11.16-0+deb10u1) ... Setting up mariadb-server-10.7 (1:10.7.4+maria~buster) ... Installing new version of config file /etc/mysql/debian-start ... mariadb-extra.socket is a disabled or a static unit not running, not starting it. mariadb-extra.socket is a disabled or a static unit, not starting it. Setting up php8.1-cli (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up php8.1-dev (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up libavfilter7:amd64 (7:4.1.9-0+deb10u1) ... Setting up mariadb-server (1:10.7.4+maria~buster) ... Setting up php8.1-fpm (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Setting up php8.1 (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for libc-bin (2.28-10+deb10u1) ... Processing triggers for systemd (241-7~deb10u8) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for mime-support (3.62) ... Processing triggers for php8.1-cli (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... Processing triggers for php8.1-fpm (8.1.6-1+0~20220517.17+debian10~1.gbp6b3bd1) ... root@http-msh02:~# apt-cache policy libmariadb-dev libmariadb-dev-compat libmariadb3 mariadb-client mariadb-client-10.7 mariadb-client-core-10.7 mariadb-common mariadb-server mariadb-server-10.7 mariadb-server-core-10.7 mysql-common libmariadb-dev: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1:10.3.34-0+deb10u1 500 500 http://debmirror.tuxis.nl/debian buster/main amd64 Packages 1:10.3.25-0+deb10u1 500 500 http://security.debian.org/debian-security buster/updates/main amd64 Packages libmariadb-dev-compat: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1:10.3.34-0+deb10u1 500 500 http://debmirror.tuxis.nl/debian buster/main amd64 Packages 1:10.3.25-0+deb10u1 500 500 http://security.debian.org/debian-security buster/updates/main amd64 Packages libmariadb3: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1:10.3.34-0+deb10u1 500 500 http://debmirror.tuxis.nl/debian buster/main amd64 Packages 1:10.3.25-0+deb10u1 500 500 http://security.debian.org/debian-security buster/updates/main amd64 Packages mariadb-client: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages 1:10.3.34-0+deb10u1 500 500 http://debmirror.tuxis.nl/debian buster/main amd64 Packages 1:10.3.25-0+deb10u1 500 500 http://security.debian.org/debian-security buster/updates/main amd64 Packages mariadb-client-10.7: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages mariadb-client-core-10.7: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages mariadb-common: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages 1:10.3.34-0+deb10u1 500 500 http://debmirror.tuxis.nl/debian buster/main amd64 Packages 1:10.3.25-0+deb10u1 500 500 http://security.debian.org/debian-security buster/updates/main amd64 Packages mariadb-server: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages 1:10.3.34-0+deb10u1 500 500 http://debmirror.tuxis.nl/debian buster/main amd64 Packages 1:10.3.25-0+deb10u1 500 500 http://security.debian.org/debian-security buster/updates/main amd64 Packages mariadb-server-10.7: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages mariadb-server-core-10.7: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages mysql-common: Installed: 1:10.7.3+maria~buster Candidate: 1:10.7.4+maria~buster Version table: 1:10.7.4+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages *** 1:10.7.3+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages 100 /var/lib/dpkg/status 1:10.7.1+maria~buster 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages 5.8+1.0.5 500 500 http://debmirror.tuxis.nl/debian buster/main amd64 Packages root@http-msh02:~# apt-cache policy Package files: 100 /var/lib/dpkg/status release a=now 500 https://packages.sury.org/php buster/main amd64 Packages release o=deb.sury.org,a=buster,n=buster,c=main,b=amd64 origin packages.sury.org 500 https://packagecloud.io/sensu/stable/debian buster/main amd64 Packages release v=1,o=packagecloud.io/sensu/stable,a=buster,n=buster,l=stable,c=main,b=amd64 origin packagecloud.io 500 http://nginx.org/packages/mainline/debian buster/nginx amd64 Packages release v=10.0,o=nginx,a=stable,n=buster,l=nginx,c=nginx,b=amd64 origin nginx.org 100 http://debmirror.tuxis.nl/debian buster-backports/main amd64 Packages release o=Debian Backports,a=buster-backports,n=buster-backports,l=Debian Backports,c=main,b=amd64 origin debmirror.tuxis.nl 500 https://deb.nodesource.com/node_16.x buster/main amd64 Packages release o=Node Source,n=buster,l=Node Source,c=main,b=amd64 origin deb.nodesource.com 500 https://artifacts.elastic.co/packages/7.x/apt stable/main amd64 Packages release o=elastic,a=stable,n=stable,l=. stable,c=main,b=amd64 origin artifacts.elastic.co 500 https://apt.tuxis.nl/tuxis monitoring/main amd64 Packages release o=tuxis monitoring,a=monitoring,n=monitoring,l=tuxis monitoring,c=main,b=amd64 origin apt.tuxis.nl 500 https://apt.tuxis.nl/tuxis tuxis-cron/main amd64 Packages release o=tuxis tuxis-cron,a=tuxis-cron,n=tuxis-cron,l=tuxis tuxis-cron,c=main,b=amd64 origin apt.tuxis.nl 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main ppc64el Packages release o=MariaDB,n=buster,l=MariaDB,c=main,b=ppc64el origin ams2.mirrors.digitalocean.com 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main arm64 Packages release o=MariaDB,n=buster,l=MariaDB,c=main,b=arm64 origin ams2.mirrors.digitalocean.com 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.7/debian buster/main amd64 Packages release o=MariaDB,n=buster,l=MariaDB,c=main,b=amd64 origin ams2.mirrors.digitalocean.com 500 http://debmirror.tuxis.nl/debian buster-updates/main amd64 Packages release o=Debian,a=oldstable-updates,n=buster-updates,l=Debian,c=main,b=amd64 origin debmirror.tuxis.nl 500 http://security.debian.org/debian-security buster/updates/main amd64 Packages release v=10,o=Debian,a=oldstable,n=buster,l=Debian-Security,c=main,b=amd64 origin security.debian.org 500 http://debmirror.tuxis.nl/debian buster/main amd64 Packages release v=10.12,o=Debian,a=oldstable,n=buster,l=Debian,c=main,b=amd64 origin debmirror.tuxis.nl Pinned packages: ``` -- With kind regards, William Edwards

1 0

[Maria-discuss] In memory DB, how to in MariaDB?
by Eliezer Croitoru 23 May '22

23 May '22

I have seen the next blog post which had a video at 2014: https://blogs.oracle.com/pcoe/post/the-future-of-the-database-begins The demo video was removed from YouTube for some reason but I had a copy of it at: https://cloud1.ngtech.co.il/static/oracle/Oracle%20Database%20In-Memory%20Po wering%20the%20Real-Time%20Enterprise%20.mp4 I am not a MariaDB or MySQL or DB in general expert and was wondering if there is something these days in MariaDB that can be used in comparison to what Oracle DB demo shows? I have used LevelDB as a backend in a customized DB and it worked very very fast and it is great. With batches it works even faster but in general it works faster then standard MariaDB setups I have implemented. So what are the options? I have millions of values and I would like to be able to insert and select as fast as possible on a single DB Server. Currently I am using a Caching tier with a specific TTL to lower the stress off the DB, but, is I possible to make the DB Faster like maybe with some writeback (leaving aside fault tolerance for speed). Thanks, Eliezer ---- Eliezer Croitoru NgTech, Tech Support Mobile: +972-5-28704261 Email: <mailto:ngtech1ltd@gmail.com> ngtech1ltd(a)gmail.com

3 4

[Maria-discuss] Debian revision should not contain codename
by William Edwards 19 May '22

19 May '22

Hi, I'm attempting to upgrade a machine with MariaDB 10.6 from Buster to Bullseye using the official MariaDB repo. I was surprised to see that apt wanted to downgrade a few packages: ``` $ apt upgrade --without-new-pkgs The following packages will be DOWNGRADED: libmariadb-dev libmariadb-dev-compat libmariadb3 mysql-common ``` I was confused at first, as the priority of the candidate is higher, and the epoch is unchanged, and the upstream version is unchanged: ``` $ apt policy mysql-common mysql-common: Installed: 1:10.6.7+maria~buster Candidate: 1:10.6.7+maria~bullseye Version table: *** 1:10.6.7+maria~buster 100 100 /var/lib/dpkg/status 1:10.6.7+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main ppc64el Packages 1:10.6.5+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main ppc64el Packages 1:10.6.4+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main arm64 Packages 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main ppc64el Packages 5.8+1.0.7 500 500 http://debmirror.tuxis.nl/debian bullseye/main amd64 Packages $ apt policy libmariadb3 libmariadb3: Installed: 1:10.6.7+maria~buster Candidate: 1:10.6.7+maria~bullseye Version table: *** 1:10.6.7+maria~buster 100 100 /var/lib/dpkg/status 1:10.6.7+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1:10.6.5+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1:10.6.4+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1:10.5.15-0+deb11u1 500 500 http://debmirror.tuxis.nl/debian bullseye/main amd64 Packages $ apt policy libmariadb-dev-compat libmariadb-dev-compat: Installed: 1:10.6.7+maria~buster Candidate: 1:10.6.7+maria~bullseye Version table: *** 1:10.6.7+maria~buster 100 100 /var/lib/dpkg/status 1:10.6.7+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1:10.6.5+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1:10.6.4+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1:10.5.15-0+deb11u1 500 500 http://debmirror.tuxis.nl/debian bullseye/main amd64 Packages $ apt policy libmariadb-dev libmariadb-dev: Installed: 1:10.6.7+maria~buster Candidate: 1:10.6.7+maria~bullseye Version table: *** 1:10.6.7+maria~buster 100 100 /var/lib/dpkg/status 1:10.6.7+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1:10.6.5+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1:10.6.4+maria~bullseye 1000 1000 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.6/debian bullseye/main amd64 Packages 1:10.5.15-0+deb11u1 500 500 http://debmirror.tuxis.nl/debian bullseye/main amd64 Packages ``` A simulation also reported that apt would 'downgrade' to the same versions: ``` $ apt upgrade --without-new-pkgs -s Inst libmariadb-dev [1:10.6.7+maria~buster] (1:10.6.7+maria~bullseye MariaDB:ams2.mirrors.digitalocean.com [amd64]) [] Inst libmariadb-dev-compat [1:10.6.7+maria~buster] (1:10.6.7+maria~bullseye MariaDB:ams2.mirrors.digitalocean.com [amd64]) [] Inst libmariadb3 [1:10.6.7+maria~buster] (1:10.6.7+maria~bullseye MariaDB:ams2.mirrors.digitalocean.com [amd64]) Inst mysql-common [1:10.6.7+maria~buster] (1:10.6.7+maria~bullseye MariaDB:ams2.mirrors.digitalocean.com [all]) ``` Some folks on IRC pointed me to the fact that the Debian revision has been updated from `maria~buster` to `maria~bullseye`. The following documentation at https://www.debian.org/doc/debian-policy/ch-controlfields.html#special-vers… says: > The lexical comparison is a comparison of ASCII values modified so that > all the letters sort earlier than all the non-letters and so that a > tilde sorts before anything, even the end of a part. 'bul' comes before 'bus', so the package for Bullseye is perceived as older, despite it being the same effective upstream version... According to https://www.debian.org/doc/debian-policy/ch-controlfields.html#special-vers…, the Debian revision should NOT contain the Debian release codename. This problem will re-appear with Bookworm. Could the package maintainer(s) attend to this? -- With kind regards, William Edwards

2 2

Re: [Maria-discuss] MariaDB latest source tarballs missing
by Sergei Golubchik 19 May '22

19 May '22

Hi, Shreenidhi, On May 19, Shreenidhi Shedi wrote: > > I am from VMware Photon OS engineering team. > > We are trying to fix few CVEs that are being reported in 10.2.x & > 10.3.x versions of MariaDB. > > There is release note for v10.2.44 but I cannot find the source > tarball in downloads page or in github tags of maria db server. You cannot find it, because it wasn't released yet. > https://mariadb.com/kb/en/mariadb-10244-release-notes/ This page says, on the very top, in a red box: Note: This page describes features in the source repository for MariaDB 10.2. There are currently no official packages or binaries available for download which contain the features. If you want to try out any of the new features described here you will need to get and compile the code yourself. > Can you guys please help me out here? Where can I get the latest > released source tarballs? https://mariadb.org/download/ > Also, when can we expect a fix for this? If at all this is not > released, when can we expect next release of MariaDB server versions? Any day now. Regards, Sergei VP of MariaDB Server Engineering and security(a)mariadb.org

1 0

[Maria-discuss] Galera: jump through major versions at once
by William Edwards 19 May '22

19 May '22

Hi, Does Galera support rolling upgrades between multiple major versions? I will be upgrading my Galera cluster from MariaDB 10.3.34 to 10.6.x. It'd save a lot of time to jump straight from 10.3 to 10.6 instead of upgrading 10.3 -> 10.4 -> 10.5 -> 10.6. The documentation at https://mariadb.com/kb/en/upgrading-from-mariadb-103-to-mariadb-104-with-ga… implies that the MariaDB version is irrelevant, and only the Galera version matters. > Next, make sure that the Galera version numbers are compatible. > > If you are upgrading from the most recent MariaDB 10.3 release to > MariaDB 10.4, then the versions will > be compatible. MariaDB 10.3 uses Galera 3 (i.e. Galera wsrep provider > versions 25.3.x), and MariaDB > 10.4 uses Galera 4 (i.e. Galera wsrep provider versions 26.4.x). This > means that upgrading to MariaDB > 10.4 also upgrades the system to Galera 4. However, Galera 3 and Galera > 4 should be compatible for the > purposes of a rolling upgrade, as long as you are using Galera 26.4.2 > or later. -- With kind regards, William Edwards

2 3

[Maria-discuss] FLUSH TABLES ... FOR EXPORT SLOW
by mariadb＠Biblestuph.com 18 May '22

18 May '22

I've recently updated from 10.3.14 => 10.6.7, and am running into an issue where FLUSH TABLES ... FOR EXPORT is sometimes very slow on large tables. One particular table that it seems to happen on often is over 20G. It doesn't hang, per se; it will complete eventually, but can take an hour or more. 2022-05-17 0:14:06 105636 [Note] InnoDB: Sync to disk of `MyDB`.`t1` started. 2022-05-17 0:14:06 105636 [Note] InnoDB: Writing table metadata to './MyDB/t1.cfg' 2022-05-17 0:14:06 105636 [Note] InnoDB: Table `MyDB`.`t1` flushed to disk 2022-05-17 0:14:06 105636 [Note] InnoDB: Sync to disk of `MyDB`.`t2` started. 2022-05-17 1:49:53 105636 [Note] InnoDB: Writing table metadata to './MyDB/t2.cfg' 2022-05-17 1:49:53 105636 [Note] InnoDB: Table `MyDB`.`t2` flushed to disk in the above the obfuscated table name t2 took about 1.5 hours to complete. In the previous version (10.3.14), these were always nearly instantaneous, even for the largest tables. At the time I'm executing the FLUSH TABLES the slave is stopped on the DB and there are no other users logged in to the DB (other than myself). I know from the docs that FLUSH TABLES has seen changes since my previous version, but I'm not clear as to what the process is waiting for (or how to avoid it). Shutting down the server first (I have innodb_fast_shutdown = 0) seems to prevent it; and the shutdown generally only takes 5-10 minutes or so. But I'd rather not shutdown if I don't have to (and I'm not 100% convinced that I won't someday see the issue in that scenario, as well). I've also tried this sequence thinking it might help: ---> STOP SLAVE Wed May 18 10:30:13 2022 ---> SLAVE STOPPED Wed May 18 10:30:13 2022 ---> FLUSH LOCAL TABLES WITH READ LOCK Wed May 18 10:30:14 2022 ---> UNLOCK TABLES Wed May 18 10:30:15 2022 ---> SET GLOBAL innodb_purge_rseg_truncate_frequency = 1 Wed May 18 10:30:15 2022 ---> SET GLOBAL innodb_max_purge_lag_wait = 0 Wed May 18 10:30:15 2022 ---> FLUSH TABLES ... FOR EXPORT Wed May 18 10:30:15 2022 but the FLUSH TABLES FOR EXPORT still waits on that large table. Is there a way to make this happen quicker without requiring the DB to be shutdown first? Or am I missing something else in the process? Thanks, Dan

1 0

[Maria-discuss] A federation bug was identified.
by 최혁규 11 May '22

11 May '22

A federation bug was identified. I have confirmed that the select where query does not work in the multi index field of some federated tables. A field in the table is used as a multi index. My server version : 10.8.2-MariaDB However, there is no problem with the server used in the previous version. The previous version is Server version: 10.5.10-MariaDB. The tested method was compared by creating a federated table on two servers with different versions. 1. 10.5.10 - MariaDB -> All queries are normally searched. 2. 10.8.2 - MariaDB -> Symptoms were confirmed in some multi index types. --> The table field datatype is (int, datetime) This is the table I created and the select query. Table Created CREATE TABLE `fd_partner_detail` ( `partner_id` varchar(100) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '파트너ID', `business_name` varchar(45) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '사업자상호명', `business_no` varchar(45) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '사업자번호', `online_marketing_business_no` varchar(45) NOT NULL DEFAULT '' COMMENT '통신판매업 신고번호', `representative` varchar(45) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '대표자명', `business_category` char(50) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '종목', `business_status` char(50) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '업종형태', `contact` varchar(45) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '연락처', `courier_code` varchar(45) NOT NULL DEFAULT '0' COMMENT '택배사코드', `postal_code` varchar(45) DEFAULT NULL COMMENT '우편번호', `address` varchar(45) DEFAULT NULL COMMENT '주소(도로명)', `address_detail` varchar(45) DEFAULT NULL COMMENT '상세주소', `officer` varchar(45) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '대표담당자명', `officer_contact` varchar(45) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '대표담당자연락처', `officer_email` varchar(45) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '대표담당자이메일', `order_officer` varchar(45) CHARACTER SET utf8mb3 DEFAULT '' COMMENT '발주담당자명', `order_officer_contact` varchar(45) CHARACTER SET utf8mb3 DEFAULT '' COMMENT '발주담당자연락처', `order_officer_email` varchar(45) CHARACTER SET utf8mb3 DEFAULT '' COMMENT '발주담당자이메일', `calculate_order_officer` varchar(45) CHARACTER SET utf8mb3 DEFAULT '' COMMENT '정산담당자명', `calculate_officer_contact` varchar(45) CHARACTER SET utf8mb3 DEFAULT '' COMMENT '정산담당자연락처', `calculate_officer_email` varchar(45) CHARACTER SET utf8mb3 DEFAULT '' COMMENT '정산담당자이메일', `cs_order_officer` varchar(45) CHARACTER SET utf8mb3 DEFAULT '' COMMENT 'CS담당자명', `cs_officer_contact` varchar(45) CHARACTER SET utf8mb3 DEFAULT '' COMMENT 'CS담당자연락처', `cs_officer_email` varchar(45) CHARACTER SET utf8mb3 DEFAULT '' COMMENT 'CS담당자이메일', `product_name` varchar(100) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '대표상품명', `product_url` varchar(255) CHARACTER SET utf8mb3 NOT NULL DEFAULT '' COMMENT '대표상품URL', `product_type` int(1) NOT NULL DEFAULT 0 COMMENT '대표상품제조구분 (1: 제조, 2:벤더)', `add_product_name_1` varchar(100) CHARACTER SET utf8mb3 DEFAULT '' COMMENT '선택상품명1', `add_product_url_1` varchar(255) CHARACTER SET utf8mb3 DEFAULT '' COMMENT '선택상품URL1', `add_product_type_1` int(1) DEFAULT 0 COMMENT '선택상품제조구분1', `add_product_name_2` varchar(100) CHARACTER SET utf8mb3 DEFAULT '' COMMENT '선택상품명2', `add_product_url_2` varchar(255) CHARACTER SET utf8mb3 DEFAULT '' COMMENT '선택상품URL2', `add_product_type_2` int(1) DEFAULT 0 COMMENT '선택상품제조구분2', `calculate_bank_code` varchar(45) NOT NULL DEFAULT '' COMMENT '정산은행코드', `calculate_bank_no` varchar(45) NOT NULL DEFAULT '' COMMENT '정산계좌번호', `calculate_bank_name` varchar(45) NOT NULL DEFAULT '' COMMENT '정산예금주명', `file_bankbook` varchar(255) DEFAULT '' COMMENT '통장사본', `original_bankbook` varchar(255) DEFAULT '' COMMENT '통장사본원본명', `file_business_license` varchar(255) DEFAULT '' COMMENT '사업자등록증', `original_business_license` varchar(255) DEFAULT '' COMMENT '사업자등록증원본명', `file_document` varchar(255) DEFAULT '' COMMENT '기타서류', `original_document` varchar(255) DEFAULT '' COMMENT '기타서류원본명', `is_terms_service` int(1) NOT NULL DEFAULT 0 COMMENT '쇼핑몰이용약관동의여부', `is_privacy_consent` int(1) NOT NULL DEFAULT 0 COMMENT '개인정보처리방침동의여부', `join_status` int(1) NOT NULL DEFAULT 1 COMMENT '가입승인상태(1: 입점대기, 2: 입점반려, 3:입점승인, 4:입점불가)', `return_cause` text CHARACTER SET utf8mb3 DEFAULT NULL COMMENT '가입반려사유', `calculate_type` int(1) NOT NULL DEFAULT 1 COMMENT '정산주기유형(1:15일, 2:30일)', `dormant_change_date` datetime DEFAULT NULL COMMENT '휴면전환일', `dormant_cancel_date` datetime DEFAULT NULL COMMENT '휴면해제일', `join_date` datetime DEFAULT NULL COMMENT '가입승인일', `is_withdraw` int(1) NOT NULL DEFAULT 0 COMMENT '탈퇴회원여부', `introduce` text DEFAULT NULL COMMENT '회사소개', `memo` varchar(255) DEFAULT '' COMMENT '관리자 메모', `corporation_code` varchar(45) CHARACTER SET utf8mb3 NOT NULL COMMENT '회사코드', `marketplace_code` varchar(45) CHARACTER SET utf8mb3 NOT NULL COMMENT '쇼핑몰코드', `is_abolished` int(1) NOT NULL DEFAULT 0 COMMENT '삭제여부', `is_popup` int(1) DEFAULT 0 COMMENT '입점 승인', `application_code` varchar(45) CHARACTER SET utf8mb3 DEFAULT NULL COMMENT '어플리케이션코드', `created_by` varchar(45) CHARACTER SET utf8mb3 DEFAULT NULL COMMENT '생성자', `created_date` datetime DEFAULT NULL COMMENT '생성일', `modified_by` varchar(45) CHARACTER SET utf8mb3 DEFAULT NULL COMMENT '수정자', `modified_date` datetime DEFAULT NULL COMMENT '수정일', `abolished_by` varchar(45) CHARACTER SET utf8mb3 DEFAULT NULL COMMENT '삭제자', `abolished_date` datetime DEFAULT NULL COMMENT '삭제일', PRIMARY KEY (`partner_id`), KEY `IDX_R_1` (`is_abolished`), KEY `IDX_R_2` (`created_date`), KEY `IDX_U_1` (`courier_code`), KEY `IDX_U_2` (`postal_code`), KEY `IDX_U_3` (`calculate_bank_code`) ) ENGINE=FEDERATED DEFAULT CHARSET=utf8mb4 ROW_FORMAT=DYNAMIC COMMENT='파트너상세정보' CONNECTION='fdc_partner_bh/fo_partner_detail' Table Select Query SELECT business_no, representative, business_name, contact, partner_id ,is_abolished FROM fd_partner_detail WHERE created_date = '1'; Select Query Result business_no representative business_name contact partner_id is_abolished ----------- -------------- ------------- ------- ---------- -------------- I want to know if what I checked is a bug.

2 1