Differences between revisions 25 and 26
Revision 25 as of 2021-09-15 05:02:52
Size: 4532
Editor: ?OttoKekalainen
Revision 26 as of 2021-09-15 05:05:20
Size: 4515
Editor: ?OttoKekalainen
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
'''See new wiki page at https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/MariaDB-in-Debian''' '''See new wiki page at https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/'''

Translation(s): none

Debian MySQL FAQ.

See new wiki page at https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/

One way you can contribute to the Debian MySQL is by turning bug reports tagged "wontfix" into FAQ entries. If the entries are good enough we would close the bug report. In such cases please make sure that the FAQ entry links back to the original bug report.

Q: How does the defaul-mysql-server meta package work?

This meta package (and -client and others) point to the MySQL/MariaDB version the Debian release team has decided is the default version. It can be used by packagers to mark dependencies. For more information see https://wiki.debian.org/Teams/MySQL/virtual-mysql-server.

Q: How does the virtual-mysql-server meta package work?

This virtual package (and -client and others) is provided by all MySQL/MariaDB versions and is used to satisfy alternative dependencies. For more information see https://wiki.debian.org/Teams/MySQL/virtual-mysql-server.

Q: The server won't start/upgrade/install

Take a look here for common causes and resolutions.

Q1: Why is the HTML documentation not packaged?

#335219 The HTML based documentation does not meet Debian's strict DFSG requirements. It would be really great if someone could write up the history of this.

Q2: Where is the NDB Cluster engine?

#459543 MySQL Cluster has been branched split into a separate product. It is not possible to include it in the MySQL Server package, a separate MySQL Cluster package must be build. Since there is overlap/conflict between the two products this is not trivial to do. Since the Wheezy freeze has occurred, it is unlikely to be included in the Wheezy release (unless later supported through backports).

See Proposals/MysqlCluster

Q3: How do I use the test suite?

#366701 The test suite enables you to run the same tests as the upstream developers use to validate a new version of MySQL. Having installed the test suite package the following should be enough:

  • cd /usr/lib/mysql-testsuite

  • ./mysql-test-run --vardir=[suitable directory with lots of space]

Q4: What are Linux Native threads?

#672675 Since 5.5 MySQL on Linux uses Linux native threads or asynchronous input-output. This usually offers improved performance in a database but may not be right for everyone. You can turn them off by setting innodb_use_native_aio=0 in the mysqld section of the config file.

Q5: My install failed to create a 'root' user. What happened?

#545741 This seems to happen where only the UNIX root can create files in /tmp. It is hard to see how such a system could really be usable.

Q6: Why does "mysql -h localhost" not use the network?

#294940 Unix Sockets are more efficient and secure and MySQL tries to use them if possible. If you really insist you can force the protocol use the '--protocol' argument.

Q7: How does one package and build server plugins?

#409389 Currently the recommended practice is to follow the example of handlersocket and depend on the mysql-source-* package. However not everyone is happy with this solution. See this discussion for more information.

Q8: Why is Debian MySQL not linked against openssl?

#630625 It would solve a few issues. Openssl seems to be somewhat more robust than yaSSL. The issue is that MySQL is primarily published under a GPL license and openssl under an incompatible BSD-style license. There are various special clauses to facilitate the combination but not everything that builds against MySQL in Debian can use those clauses. If this causes you an issue you can always recompile against openssl for your own purposes.