After you select the MySQL installation version, the second decision is whether to use the source code distribution version or the binary distribution version. In most cases, if your platform already has a binary distribution version, you may use the binary distribution version. Most platforms can use the original binary distribution version, such as Linux using RPM files, MacOSX using DMG to install software
After you select the MySQL installation version, the second decision is whether to use the source code distribution version or the binary distribution version. In most cases, if your platform already has a binary distribution version, you may use the binary distribution version. Most platforms can use the original binary distribution version. For example, Linux uses RPM files and Mac OS X uses DMG to install software.
After you select the MySQL installation version, the second decision is whether to use the source code distribution version or the binary distribution version. In most cases, if your platform already has a binary distribution version, you may use the binary distribution version. Most platforms can use the original binary distribution version. For example, Linux uses RPM files and Mac OS X uses DMG to install software packages. You can also use Zip files or compressed tar files.
Reasons for choosing the binary distribution edition:
◆ The binary distribution version is easier to install than the source code distribution version.
◆ To meet the needs of different users, we provide two different binary versions: A compiled non-transaction storage engine (a small quick library ), another important extension option, such as the transaction security table, is configured. Both versions are compiled from the same source code distribution version. All local MySQL clients can connect to any version of MySQL server. The extended MySQL database distribution version is marked with the-max suffix and is configured with the same options as mysqld-max. To use MySQL-Max RPM, you must first install standard MySQL-server RPM.
In some environments, it is best to install the source code distribution version MySQL:
◆ You want to install MySQL in an obvious position. The standard binary distribution can be installed anywhere, but you want to put the MySQL component somewhere more flexibly.
◆ You want to configure some special features not included in the standard binary distribution edition for mysqld. The following are some of the most common options you want to use:
◆ -- With-innodb (used by default in all MySQL 5.1 database versions)
◆ -- With-berkeley-db (applicable only to some platforms)
◆ -- With-libwrap
◆ -- With-name d-z-libs (applicable to some binary systems)
◆ -- With-debug [= full]
◆ You want to configure some special features already included in the standard binary distribution version of mysqld. For example, a compiled distribution version supports all character sets. If you want a smaller MySQL server, you can recompile and only support the character set you need.
◆ You have a dedicated Compiler (such as pgcc) or want to use compiler options that better optimize your processor. The binary distribution edition Compilation option is suitable for various processors of the same processor family.
◆ You want to use the latest source code in the BitKeeper library to access all the latest vulnerability fixes. For example, if you discover a vulnerability and report it to the MySQL Development Team, and the vulnerability fix is passed to the source code library, you can access it. The vulnerability is fixed only after the release.
◆ If you want to read (or modify) the C and C ++ code of MySQL, you should obtain the source code distribution version. The source code is always the final manual. The source code distribution version also contains more tests and instances than the binary distribution version.
[Related articles]
- MySQL database backup solution details
- MySQL Data Backup System Solution
- Simple MySQL backup method (1)
[Responsible editor: bihai blue sky TEL :( 010) 68476606]