mirror of
https://github.com/MariaDB/server.git
synced 2026-10-23 18:49:29 +03:00
8923afa5c2
scripts/fill_help_tables.sql from https://github.com/mariadb-corporation/mariadb-docs/ as of 3fb208fcdfed06beb52ef9e305017de2387ff012 Other URL changes are taken from the HTTP redirection URL from the old KB. Some test cases where impacted: * ps_missed_cmds{,_bin_prot} - used a topic_id of 0 that is now used, used MAX_INT instead. * range_notembedded used the help data as a test case. As its not a stable table data, replaces with static data. Test case valid by ensuring the ANALYZE EXPLAIN and optimizer trace had the same structure. Also valided the MDEV-24739/MDEV-25069 bug fixes from where the test case originaled, when reverted, exhibited the previous behavour before the bug fixes.
23 lines
1.1 KiB
Plaintext
23 lines
1.1 KiB
Plaintext
#
|
|
# NOTE: This file is read only by the traditional SysV init script.
|
|
# Debian 9 and Ubuntu 17.04 onward do not normally read this file as they use
|
|
# systemd by default.
|
|
#
|
|
# For similar behavior, systemd users should override ExecStart by dropping
|
|
# files into /etc/systemd/system/mariadb.service.d/
|
|
#
|
|
# See also:
|
|
# https://wiki.debian.org/Teams/pkg-systemd/Packaging#overriding_options_and_.2Fetc.2Fdefault_handling
|
|
# https://mariadb.com/docs/server/server-management/starting-and-stopping-mariadb/systemd
|
|
#
|
|
# Note also that MariaDB systemd does _not_ utilize mysqld_safe.
|
|
|
|
# The delay in seconds the init script waits for the server to be up and running after having started "mysqld_safe" to run the "/etc/mysql/debian-start" script.
|
|
# If the server is still not responding after the delay, the script won't be executed and an error will be thrown on the syslog.
|
|
# Default: 30
|
|
#MYSQLD_STARTUP_TIMEOUT=30
|
|
|
|
# The email recipient(s) of the output of the check for crashed and improperly closed MyISAM and Aria tables done at each server start by the "/etc/mysql/debian-start" script.
|
|
# Default: root
|
|
#MYCHECK_RCPT="root"
|