AI导航网
微信公众号搜"智元新知"关注
微信扫一扫可直接关注哦！

debian – MySQL / Maria数据库无法加载：/var/run/mysqld/mysqld.sock(2“没有这样的文件或目录”)

分类：Mariadb作者：编程之家原文地址

建立

>服务器电脑

>发行版：Raspbian GNU / Linux 8
>内核：4.9.35-v7 armv7l(32位)

我的MySQL数据库没有加载

admin@Xroklaus:~ $sudo systemctl status MysqL
● MysqL.service - LSB: Start and stop the MysqL database server daemon
   Loaded: loaded (/etc/init.d/MysqL)
   Active: Failed (Result: exit-code) since Thu 2018-01-11 01:09:32 UTC; 6h ago
  Process: 914 ExecStart=/etc/init.d/MysqL start (code=exited, status=1/FAILURE)

Jan 11 01:08:48 Xroklaus systemd[1]: Starting LSB: Start and stop the MysqL database server daemon...
Jan 11 01:09:32 Xroklaus MysqL[914]: Starting MariaDB database server: MysqLd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failed!
Jan 11 01:09:32 Xroklaus systemd[1]: MysqL.service: control process exited, code=exited status=1
Jan 11 01:09:32 Xroklaus systemd[1]: Failed to start LSB: Start and stop the MysqL database server daemon.
Jan 11 01:09:32 Xroklaus systemd[1]: Unit MysqL.service entered Failed state.

错误日志

admin@Xroklaus:~ $sudo cat /var/lib/MysqL/Xroklaus.err
180111  1:04:39 [ERROR] Can't open the MysqL.plugin table. Please run MysqL_upgrade to create it.
180111  1:04:39 [Note] Server socket created on IP: '::'.
180111  1:04:39 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect file format 'host'
180111 01:04:39 MysqLd_safe MysqLd from pid file /var/lib/MysqL/Xroklaus.pid ended
180111 01:08:53 MysqLd_safe Starting MysqLd daemon with databases from /var/lib/MysqL
180111  1:08:53 [Note] /usr/sbin/MysqLd (MysqLd 10.0.32-MariaDB-0+deb8u1) starting as process 1347 ...
180111  1:08:54 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

180111  1:08:54 [Note] InnoDB: Using mutexes to ref count buffer pool pages
180111  1:08:54 [Note] InnoDB: The InnoDB memory heap is disabled
180111  1:08:54 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
180111  1:08:54 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
180111  1:08:54 [Note] InnoDB: Compressed tables use zlib 1.2.8
180111  1:08:54 [Note] InnoDB: Using Linux native AIO
180111  1:08:54 [Note] InnoDB: Not using cpu crc32 instructions
180111  1:08:54 [Note] InnoDB: Initializing buffer pool, size = 128.0M
180111  1:08:54 [Note] InnoDB: Completed initialization of buffer pool
180111  1:08:54 [Note] InnoDB: Highest supported file format is Barracuda.
180111  1:08:54 [Note] InnoDB: The log sequence numbers 1616887 and 1616887 in ibdata files do not match the log sequence number 1616913 in the ib_logfiles!
180111  1:08:54 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
180111  1:08:55 [Note] InnoDB: 128 rollback segment(s) are active.
180111  1:08:55 [Note] InnoDB: Waiting for purge to start
180111  1:08:55 [Note] InnoDB:  Percona XTradB (http://www.percona.com) 5.6.36-82.1 started; log sequence number 1616913
180111  1:08:55 [Note] Plugin 'FeedBACK' is disabled.
180111  1:08:55 [ERROR] Can't open the MysqL.plugin table. Please run MysqL_upgrade to create it.
180111  1:08:55 [Note] Server socket created on IP: '::'.
180111  1:08:55 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect file format 'host'
180111 01:08:55 MysqLd_safe MysqLd from pid file /var/lib/MysqL/Xroklaus.pid ended

看起来它缺少一个文件.

admin@Xroklaus:~ $sudo MysqL_upgrade
Version check Failed. Got the following error when calling the 'MysqL' command line client
ERROR 2002 (HY000): Can't connect to local MysqL server through socket '/var/run/MysqLd/MysqLd.sock' (2 "No such file or directory")
Fatal error: Upgrade Failed

[更新]

我能用MysqLd_safe –skip-grant-tables运行daeman,
但升级失败：

admin@Xroklaus:~ $sudo MysqL_upgrade
Phase 1/6: Checking and upgrading MysqL database
Processing databases
MysqL
MysqL.column_stats                                 OK
MysqL.columns_priv
Error    : Incorrect file format 'columns_priv'
error    : Corrupt
MysqL.db
Error    : Incorrect file format 'db'
error    : Corrupt
MysqL.event
Error    : Incorrect file format 'event'
error    : Corrupt
MysqL.func
Error    : Incorrect file format 'func'
error    : Corrupt
MysqL.gtid_slave_pos                               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.innodb_index_stats                           OK
MysqL.innodb_table_stats                           OK
MysqL.plugin
Error    : Incorrect file format 'plugin'
error    : Corrupt
MysqL.proc                                         OK
MysqL.procs_priv
Error    : Incorrect file format 'procs_priv'
error    : Corrupt
MysqL.proxies_priv                                 OK
MysqL.roles_mapping                                OK
MysqL.servers                                      OK
MysqL.table_stats                                  OK
MysqL.tables_priv
Error    : Incorrect file format 'tables_priv'
error    : Corrupt
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
Error    : Incorrect file format 'user'
error    : Corrupt

Repairing tables
MysqL.columns_priv
Error    : Incorrect file format 'columns_priv'
error    : Corrupt
MysqL.db
Error    : Incorrect file format 'db'
error    : Corrupt
MysqL.event
Error    : Incorrect file format 'event'
error    : Corrupt
MysqL.func
Error    : Incorrect file format 'func'
error    : Corrupt
MysqL.plugin
Error    : Incorrect file format 'plugin'
error    : Corrupt
MysqL.procs_priv
Error    : Incorrect file format 'procs_priv'
error    : Corrupt
MysqL.tables_priv
Error    : Incorrect file format 'tables_priv'
error    : Corrupt
MysqL.user
Error    : Incorrect file format 'user'
error    : Corrupt
Phase 2/6: Fixing views
Phase 3/6: Running 'MysqL_fix_privilege_tables'
ERROR 130 (HY000) at line 141: Incorrect file format 'user'
ERROR 130 (HY000) at line 143: Incorrect file format 'user'
ERROR 130 (HY000) at line 144: Incorrect file format 'user'
ERROR 130 (HY000) at line 146: Incorrect file format 'db'
ERROR 130 (HY000) at line 147: Incorrect file format 'user'
ERROR 130 (HY000) at line 148: Incorrect file format 'db'
ERROR 130 (HY000) at line 150: Incorrect file format 'user'
ERROR 130 (HY000) at line 155: Incorrect file format 'user'
ERROR 130 (HY000) at line 156: Incorrect file format 'tables_priv'
ERROR 130 (HY000) at line 158: Incorrect file format 'tables_priv'
ERROR 130 (HY000) at line 166: Incorrect file format 'tables_priv'
ERROR 130 (HY000) at line 174: Incorrect file format 'columns_priv'
ERROR 130 (HY000) at line 177: Incorrect file format 'columns_priv'
ERROR 130 (HY000) at line 186: Incorrect file format 'columns_priv'
ERROR 130 (HY000) at line 189: Incorrect file format 'func'
ERROR 130 (HY000) at line 191: Incorrect file format 'user'
ERROR 130 (HY000) at line 192: Incorrect file format 'user'
ERROR 130 (HY000) at line 200: Incorrect file format 'user'
ERROR 130 (HY000) at line 201: Incorrect file format 'user'
ERROR 130 (HY000) at line 205: Incorrect file format 'db'
ERROR 130 (HY000) at line 211: Incorrect file format 'user'
ERROR 130 (HY000) at line 212: Incorrect file format 'db'
ERROR 130 (HY000) at line 214: Incorrect file format 'user'
ERROR 130 (HY000) at line 215: Incorrect file format 'func'
ERROR 130 (HY000) at line 216: Incorrect file format 'user'
ERROR 130 (HY000) at line 220: Incorrect file format 'user'
ERROR 130 (HY000) at line 244: Incorrect file format 'db'
ERROR 130 (HY000) at line 249: Incorrect file format 'db'
ERROR 130 (HY000) at line 279: Incorrect file format 'func'
ERROR 130 (HY000) at line 281: Incorrect file format 'func'
ERROR 130 (HY000) at line 312: Incorrect file format 'plugin'
ERROR 130 (HY000) at line 317: Incorrect file format 'user'
ERROR 130 (HY000) at line 318: Incorrect file format 'db'
ERROR 130 (HY000) at line 319: Incorrect file format 'db'
ERROR 130 (HY000) at line 322: Incorrect file format 'user'
ERROR 130 (HY000) at line 323: Incorrect file format 'user'
ERROR 130 (HY000) at line 324: Incorrect file format 'db'
ERROR 130 (HY000) at line 325: Incorrect file format 'db'
ERROR 130 (HY000) at line 328: Incorrect file format 'user'
ERROR 130 (HY000) at line 329: Incorrect file format 'user'
ERROR 130 (HY000) at line 330: Incorrect file format 'user'
ERROR 130 (HY000) at line 332: Incorrect file format 'user'
ERROR 130 (HY000) at line 333: Incorrect file format 'db'
ERROR 130 (HY000) at line 334: Incorrect file format 'db'
ERROR 130 (HY000) at line 337: Incorrect file format 'user'
ERROR 130 (HY000) at line 338: Incorrect file format 'user'
ERROR 130 (HY000) at line 339: Incorrect file format 'db'
ERROR 130 (HY000) at line 340: Incorrect file format 'db'
ERROR 130 (HY000) at line 343: Incorrect file format 'user'
ERROR 130 (HY000) at line 344: Incorrect file format 'user'
ERROR 130 (HY000) at line 345: Incorrect file format 'db'
ERROR 130 (HY000) at line 346: Incorrect file format 'db'
ERROR 130 (HY000) at line 349: Incorrect file format 'user'
ERROR 130 (HY000) at line 350: Incorrect file format 'db'
ERROR 130 (HY000) at line 352: Incorrect file format 'user'
ERROR 130 (HY000) at line 353: Incorrect file format 'user'
ERROR 130 (HY000) at line 355: Incorrect file format 'user'
ERROR 130 (HY000) at line 356: Incorrect file format 'user'
ERROR 130 (HY000) at line 357: Incorrect file format 'user'
ERROR 130 (HY000) at line 358: Incorrect file format 'user'
ERROR 130 (HY000) at line 361: Incorrect file format 'procs_priv'
ERROR 130 (HY000) at line 364: Incorrect file format 'procs_priv'
ERROR 130 (HY000) at line 367: Incorrect file format 'procs_priv'
ERROR 130 (HY000) at line 370: Incorrect file format 'procs_priv'
ERROR 130 (HY000) at line 373: Incorrect file format 'procs_priv'
ERROR 130 (HY000) at line 472: Incorrect file format 'user'
ERROR 130 (HY000) at line 473: Incorrect file format 'user'
ERROR 130 (HY000) at line 474: Incorrect file format 'user'
ERROR 130 (HY000) at line 475: Incorrect file format 'user'
ERROR 130 (HY000) at line 476: Incorrect file format 'db'
ERROR 130 (HY000) at line 477: Incorrect file format 'db'
ERROR 130 (HY000) at line 478: Incorrect file format 'event'
ERROR 130 (HY000) at line 479: Incorrect file format 'event'
ERROR 130 (HY000) at line 480: Incorrect file format 'event'
ERROR 130 (HY000) at line 481: Incorrect file format 'event'
ERROR 130 (HY000) at line 515: Incorrect file format 'event'
ERROR 130 (HY000) at line 516: Incorrect file format 'event'
ERROR 130 (HY000) at line 517: Incorrect file format 'event'
ERROR 130 (HY000) at line 518: Incorrect file format 'event'
ERROR 130 (HY000) at line 519: Incorrect file format 'event'
ERROR 130 (HY000) at line 521: Incorrect file format 'event'
ERROR 130 (HY000) at line 524: Incorrect file format 'event'
ERROR 130 (HY000) at line 526: Incorrect file format 'event'
ERROR 130 (HY000) at line 529: Incorrect file format 'event'
ERROR 130 (HY000) at line 531: Incorrect file format 'event'
ERROR 130 (HY000) at line 534: Incorrect file format 'event'
ERROR 130 (HY000) at line 536: Incorrect file format 'event'
ERROR 130 (HY000) at line 538: Incorrect file format 'event'
ERROR 130 (HY000) at line 539: Incorrect file format 'db'
ERROR 130 (HY000) at line 541: Incorrect file format 'user'
ERROR 130 (HY000) at line 542: Incorrect file format 'user'
ERROR 130 (HY000) at line 543: Incorrect file format 'user'
ERROR 130 (HY000) at line 546: Incorrect file format 'db'
ERROR 130 (HY000) at line 547: Incorrect file format 'db'
ERROR 130 (HY000) at line 548: Incorrect file format 'user'
ERROR 130 (HY000) at line 550: Incorrect file format 'user'
ERROR 130 (HY000) at line 551: Incorrect file format 'user'
ERROR 130 (HY000) at line 552: Incorrect file format 'user'
ERROR 130 (HY000) at line 553: Incorrect file format 'user'
ERROR 130 (HY000) at line 554: Incorrect file format 'user'
ERROR 130 (HY000) at line 555: Incorrect file format 'user'
ERROR 130 (HY000) at line 556: Incorrect file format 'user'
ERROR 130 (HY000) at line 557: Incorrect file format 'user'
ERROR 130 (HY000) at line 558: Incorrect file format 'user'
ERROR 130 (HY000) at line 559: Incorrect file format 'user'
ERROR 1436 (HY000) at line 574: Thread stack overrun:  4864 bytes used of a 131072 byte stack, and 0 bytes needed.  Use 'MysqLd --thread_stack=#' to specify a bigger stack.
ERROR 130 (HY000) at line 577: Incorrect file format 'user'
ERROR 130 (HY000) at line 597: Incorrect file format 'user'
ERROR 130 (HY000) at line 598: Incorrect file format 'db'
ERROR 130 (HY000) at line 599: Incorrect file format 'tables_priv'
ERROR 130 (HY000) at line 600: Incorrect file format 'columns_priv'
ERROR 130 (HY000) at line 601: Incorrect file format 'procs_priv'
ERROR 130 (HY000) at line 603: Incorrect file format 'event'
ERROR 130 (HY000) at line 608: Incorrect file format 'procs_priv'
ERROR 130 (HY000) at line 609: Incorrect file format 'tables_priv'
ERROR 130 (HY000) at line 625: Incorrect file format 'event'
ERROR 1050 (42S01) at line 644: Table 'cond_instances' already exists
ERROR 1050 (42S01) at line 669: Table 'events_waits_current' already exists
ERROR 1050 (42S01) at line 694: Table 'events_waits_history' already exists
ERROR 1050 (42S01) at line 719: Table 'events_waits_history_long' already exists
ERROR 1050 (42S01) at line 732: Table 'events_waits_summary_by_instance' already exists
ERROR 1050 (42S01) at line 745: Table 'events_waits_summary_by_host_by_event_name' already exists
ERROR 1050 (42S01) at line 758: Table 'events_waits_summary_by_user_by_event_name' already exists
ERROR 1050 (42S01) at line 772: Table 'events_waits_summary_by_account_by_event_name' already exists
ERROR 1050 (42S01) at line 785: Table 'events_waits_summary_by_thread_by_event_name' already exists
ERROR 1050 (42S01) at line 797: Table 'events_waits_summary_global_by_event_name' already exists
ERROR 1050 (42S01) at line 806: Table 'file_instances' already exists
ERROR 1050 (42S01) at line 835: Table 'file_summary_by_event_name' already exists
ERROR 1050 (42S01) at line 866: Table 'file_summary_by_instance' already exists
ERROR 1050 (42S01) at line 879: Table 'socket_instances' already exists
ERROR 1050 (42S01) at line 909: Table 'socket_summary_by_instance' already exists
ERROR 1050 (42S01) at line 938: Table 'socket_summary_by_event_name' already exists
ERROR 1050 (42S01) at line 973: Table 'host_cache' already exists
ERROR 1050 (42S01) at line 982: Table 'mutex_instances' already exists
ERROR 1050 (42S01) at line 996: Table 'objects_summary_global_by_type' already exists
ERROR 1050 (42S01) at line 1006: Table 'performance_timers' already exists
ERROR 1050 (42S01) at line 1016: Table 'rwlock_instances' already exists
ERROR 1050 (42S01) at line 1025: Table 'setup_actors' already exists
ERROR 1050 (42S01) at line 1033: Table 'setup_consumers' already exists
ERROR 1050 (42S01) at line 1042: Table 'setup_instruments' already exists
ERROR 1050 (42S01) at line 1053: Table 'setup_objects' already exists
ERROR 1050 (42S01) at line 1061: Table 'setup_timers' already exists
ERROR 1050 (42S01) at line 1106: Table 'table_io_waits_summary_by_index_usage' already exists
ERROR 1050 (42S01) at line 1150: Table 'table_io_waits_summary_by_table' already exists
ERROR 1050 (42S01) at line 1229: Table 'table_lock_waits_summary_by_table' already exists
ERROR 1050 (42S01) at line 1249: Table 'threads' already exists
ERROR 1050 (42S01) at line 1265: Table 'events_stages_current' already exists
ERROR 1050 (42S01) at line 1281: Table 'events_stages_history' already exists
ERROR 1050 (42S01) at line 1297: Table 'events_stages_history_long' already exists
ERROR 1050 (42S01) at line 1310: Table 'events_stages_summary_by_thread_by_event_name' already exists
ERROR 1050 (42S01) at line 1323: Table 'events_stages_summary_by_host_by_event_name' already exists
ERROR 1050 (42S01) at line 1336: Table 'events_stages_summary_by_user_by_event_name' already exists
ERROR 1050 (42S01) at line 1350: Table 'events_stages_summary_by_account_by_event_name' already exists
ERROR 1050 (42S01) at line 1362: Table 'events_stages_summary_global_by_event_name' already exists
ERROR 1050 (42S01) at line 1408: Table 'events_statements_current' already exists
ERROR 1050 (42S01) at line 1454: Table 'events_statements_history' already exists
ERROR 1050 (42S01) at line 1500: Table 'events_statements_history_long' already exists
ERROR 1050 (42S01) at line 1532: Table 'events_statements_summary_by_thread_by_event_name' already exists
ERROR 1050 (42S01) at line 1564: Table 'events_statements_summary_by_host_by_event_name' already exists
ERROR 1050 (42S01) at line 1596: Table 'events_statements_summary_by_user_by_event_name' already exists
ERROR 1050 (42S01) at line 1629: Table 'events_statements_summary_by_account_by_event_name' already exists
ERROR 1050 (42S01) at line 1660: Table 'events_statements_summary_global_by_event_name' already exists
ERROR 1050 (42S01) at line 1669: Table 'hosts' already exists
ERROR 1050 (42S01) at line 1678: Table 'users' already exists
ERROR 1050 (42S01) at line 1688: Table 'accounts' already exists
ERROR 1050 (42S01) at line 1723: Table 'events_statements_summary_by_digest' already exists
ERROR 1050 (42S01) at line 1733: Table 'session_connect_attrs' already exists
ERROR 1050 (42S01) at line 1739: Table 'session_account_connect_attrs' already exists
Fatal error: Upgrade Failed

[更新]

通过删除所有表来修复.

解决方法:

您的MysqL数据库已损坏.

首先备份你的/ var / lib / MysqL.

然后做：

sudo MysqLd --skip-grant-tables &

或者对于Debian

 MysqLd_safe --skip-grant-tables &

在运行它时,执行：

$MysqL
MysqL> use MysqL
MysqL> repair table host use_frm;
MysqL> exit

停止MysqLd@R_404_6363@并重启服务：

$sudo service MysqL restart

那应该暂时解决它.请注意,您很容易遇到从SD卡运行MysqL数据库的这些小问题.树莓也被称为在关闭时出现零星的SD腐败问题.

在SD卡中使用密集数据库操作也会缩短其使用寿命.

考虑将操作系统或至少MysqL DB移动到外部磁盘或USB笔.

如果您最近升级了MysqL版本,并且/或者仍然出现MysqL错误,请立即运行升级操作：

sudo MysqL_upgrade

此操作修复了在不同MysqL版本之间更改的表和内部数据表示.

PS.有可能更多的表被破坏,数据库完整性受到损害.如果数据不重要,请考虑恢复最近的MysqL数据库备份转储或从头开始创建它.

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 [email protected] 举报，一经查实，本站将立刻删除。

相关推荐

2022年-5月22日centos7网络源安装mysql
安装开始...1.打开“https://dev.mysql.com/downloadsepo/yum/”下载Mysql源      将下载好的mysql源上传linux服务器 2.yumlocalinstallmysql80*#安装源 centos7中默认安装的是mariadb数据库，如果想要安装my...
K8S Helm安装部署 MariaDB 高可用、主从集群
安装Helm3#官网下载慢#wgethttps://get.helm.sh/helm-v3.5.4-linux-amd64.tar.gzwgethttp://qiniu.dev-share.top/helm-v3.5.4-linux-amd64.tar.gztar-zxvfhelm-v3.5.4-linux-amd64.tar.gzcplinux-amd64/helm/usr/loc...
安装MariaDB后无法启动怎么解决？
通过Linux命令行启动用的指令：systemctlstartmariadb.service反馈：Failedtostartmariadb.service:Unitmariadb.servicenotfound.MariaDB简介MariaDB是MySQL的一个分支，MariaDB打算保持与MySQL的高度兼容性，确保具...
Centos7安装mariaDB
InstallingMariaDBServer10.4TodeployMariaDBCommunityServer10.4onRHEL7orCentOS7,firstdownloadandusethe mariadb_repo_setup scripttoconfiguretheMariaDBrepositoriesforYUM:$sudoyuminstallwget$wgethttps://...
MySQL存储引擎
阅读目录一什么是存储引擎二mysql支持的存储引擎三使用存储引擎一什么是存储引擎mysql中建立的库--> 文件夹库中建立的表--> 文件现实生活中我们用来存储数据的文件有不同的类型，每种文件类型对应各自不同的...
centos7 Mariadb 安装
1、安装MariaDB安装命令yum-yinstallmariadbmariadb-server安装完成MariaDB，首先启动MariaDBsystemctlstartmariadb设置开机启动systemctlenablemariadb[root@node1~]#systemctlenablemariadbCreatedsymlinkfrom/etc...
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: N
Centos7.5 刚安装的mariadb数据库报错报错:ERROR1045(28000):Accessdeniedforuser'root'@'localhost'(usingpassword:NO)原因一:没有启动数据库解决方法:systemctlstartmariadbsystemctlenablem...
mariadb多实例安装
基于YUM安装的mariadb多实例.=================================================================1.yum安装mariadb-server包#yuminstallmariadb-server2.创建多实例对应的目录结构#mkdir/mysql/{3306,3307,3308}/{d...
centos7 mysql数据库安装和配置
一、系统环境[root@localhost~]#cat/etcedhat-releaseCentOSLinuxrelease7.6.1810(Core)二、mysql安装#yuminstallmysqlmysql-servermysql-devel安装mysql-server失败，如下图：[root@localhost~]#yuminstallmysql-se...
MariaDB
数据库的选择两大点是：开源和跨平台，满足这三点MySQL、MongoDB和MariaDB。其中MariaDB是MySQL的分支，也是它的进阶产品，未来很有可能替代MySQL。与MySQL相比较，MariaDB更强的地方在于：Maria 存储引擎PBXT存储引...
    pythonJavaScriptjavaHTMLreactjsC#AndroidCSSNode.jssqlrpython-3.xMysqLjQueryc++pandasFlutterangularIOSdjangolinuxswifttypescript路由器JSON路由器设置无线路由器h3c华三华三路由器设置华三路由器电脑软件教程arraysdocker软件图文教程Cvue.jslaravelspring-bootreact-native