2020-01-12 21:19:52 +01:00
|
|
|
# $NetBSD: Makefile,v 1.29 2020/01/12 20:20:08 ryoon Exp $
|
2016-09-16 08:49:11 +02:00
|
|
|
|
|
|
|
|
PKGNAME= ${DISTNAME:S/-/-server-/}
|
2020-01-12 21:19:52 +01:00
|
|
|
PKGREVISION= 1
|
2016-09-16 08:49:11 +02:00
|
|
|
COMMENT= MySQL 5, a free SQL database (server)
|
|
|
|
|
|
|
|
|
|
CONFLICTS= mysql3-server-[0-9]*
|
|
|
|
|
|
|
|
|
|
.include "../../databases/mysql57-client/Makefile.common"
|
|
|
|
|
|
|
|
|
|
CMAKE_ARGS+= -DINSTALL_INFODIR=${PKGINFODIR}
|
|
|
|
|
|
|
|
|
|
.if !empty(PKG_OPTIONS:Membedded-server)
|
2019-11-02 16:37:59 +01:00
|
|
|
CMAKE_ARGS+= -DWITH_EMBEDDED_SERVER=ON
|
|
|
|
|
PLIST.embedded= yes
|
2016-09-16 08:49:11 +02:00
|
|
|
.else
|
2019-11-02 16:37:59 +01:00
|
|
|
CMAKE_ARGS+= -DWITH_EMBEDDED_SERVER=OFF
|
2016-09-16 08:49:11 +02:00
|
|
|
# We only need readline to placate the configure script if we don't build
|
|
|
|
|
# the embedded server as it is the only binary linked against "readline".
|
|
|
|
|
BUILDLINK_DEPMETHOD.editline= build
|
|
|
|
|
BUILDLINK_DEPMETHOD.readline= build
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
PLIST_VARS+= embedded ndb auth_socket
|
|
|
|
|
|
|
|
|
|
.if ${OPSYS} == "Linux"
|
|
|
|
|
PLIST.auth_socket= yes
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
PTHREAD_OPTS+= require
|
|
|
|
|
|
|
|
|
|
PKG_GROUPS= ${MYSQL_GROUP}
|
|
|
|
|
PKG_USERS= ${MYSQL_USER}:${MYSQL_GROUP}
|
|
|
|
|
|
|
|
|
|
PKG_GECOS.${MYSQL_USER}= MySQL database administrator
|
|
|
|
|
PKG_HOME.${MYSQL_USER}= ${MYSQL_DATADIR}
|
|
|
|
|
PKG_SHELL.${MYSQL_USER}= ${SH}
|
|
|
|
|
|
|
|
|
|
RCD_SCRIPTS= mysqld
|
|
|
|
|
SMF_NAME= mysql
|
|
|
|
|
SMF_METHODS= ${RCD_SCRIPTS}
|
|
|
|
|
|
|
|
|
|
FILES_SUBST+= HOSTNAME_CMD=${HOSTNAME_CMD:Q}
|
|
|
|
|
FILES_SUBST+= MYSQL_DATADIR=${MYSQL_DATADIR}
|
|
|
|
|
FILES_SUBST+= MYSQL_USER=${MYSQL_USER} MYSQL_GROUP=${MYSQL_GROUP}
|
|
|
|
|
FILES_SUBST+= MYSQL_PIDFILE=${MYSQL_PIDFILE}
|
|
|
|
|
MESSAGE_SUBST+= MYSQL_DATADIR=${MYSQL_DATADIR}
|
|
|
|
|
MESSAGE_SUBST+= MYSQL_USER=${MYSQL_USER} MYSQL_GROUP=${MYSQL_GROUP}
|
|
|
|
|
BUILD_DEFS+= MYSQL_DATADIR
|
|
|
|
|
|
|
|
|
|
REPLACE_PERL+= mysql-test/lib/v1/mysql-test-run.pl
|
|
|
|
|
REPLACE_PERL+= mysql-test/mysql-stress-test.pl
|
|
|
|
|
REPLACE_PERL+= mysql-test/mysql-test-run.pl
|
|
|
|
|
REPLACE_PERL+= mysql-test/suite/engines/rr_trx/run_stress_tx_rr.pl
|
|
|
|
|
REPLACE_PERL+= mysql-test/suite/funcs_1/lib/DataGen_local.pl
|
|
|
|
|
REPLACE_PERL+= mysql-test/suite/funcs_1/lib/DataGen_modify.pl
|
|
|
|
|
REPLACE_PERL+= mysql-test/suite/funcs_2/lib/gen_charset_utf8.pl
|
|
|
|
|
REPLACE_PERL+= mysql-test/suite/opt_trace/validate_json.pl
|
|
|
|
|
REPLACE_PERL+= mysql-test/suite/rpl/extension/bhs.pl
|
|
|
|
|
REPLACE_PERL+= mysql-test/suite/rpl/extension/checksum.pl
|
|
|
|
|
|
|
|
|
|
REPLACE_SH+= mysql-test/suite/rpl/t/rpl_loaddata_symlink-master.sh
|
|
|
|
|
REPLACE_SH+= mysql-test/suite/rpl/t/rpl_loaddata_symlink-slave.sh
|
|
|
|
|
REPLACE_SH+= mysql-test/suite/rpl/t/rpl_misc_functions-slave.sh
|
|
|
|
|
REPLACE_SH+= mysql-test/t/long_tmpdir-master.sh
|
|
|
|
|
REPLACE_SH+= mysql-test/t/lowercase_mixed_tmpdir-master.sh
|
|
|
|
|
REPLACE_SH+= mysql-test/t/lowercase_mixed_tmpdir_innodb-master.sh
|
|
|
|
|
|
mysql57-{client,server}: updated to 5.7.25
Changes in MySQL 5.7.25
Deprecation and Removal Notes
The resolveip and resolve_stack_dump utilities are now deprecated and will be removed in MySQL 8.0. nslookup, host, or dig can be used instead of resolveip. Stack traces from official MySQL builds are always symbolized, so there is no need to use resolve_stack_dump.
Pluggable Authentication
If the LDAP port number is configured as 636 or 3269, the plugin now uses LDAPS (LDAP over SSL) instead of LDAP. The port number is settable using the authentication_ldap_sasl_server_port or authentication_ldap_simple_server_port system variable. (LDAPS differs from startTLS.)
Previously, for LDAP authentication with proxying, LDAP authentication plugins used the first group name returned by the LDAP server as the MySQL proxy user account name. The authentication string for a MySQL account now can specify a list of groups to match, in preference order, and can optionally map the matching group name to a specified MySQL proxy user name. See LDAP Pluggable Authentication.
Security Notes
The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2q. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html.
This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead.
Functionality Added or Changed
Microsoft Windows: The access control granted to clients on the named pipe created by the MySQL server now is set to the minimum necessary for successful communication on Windows. Newer MySQL client software can open named pipe connections without any additional configuration. If older client software cannot be upgraded immediately, the new named_pipe_full_access_group server system variable can be used to give a Windows group the necessary permissions to open a named pipe connection. Membership in the full-access group should be restricted and temporary.
Bugs Fixed
InnoDB: A dangling pointer caused a memory leak.
InnoDB: An ON DELETE CASCADE operation on table with a foreign key constraint and an indexed virtual column caused the server to exit.
InnoDB: An incorrectly written DML log involving a virtual column value raised an assertion.
InnoDB: Using the O_DIRECT_NO_FSYNC innodb_flush_method setting could cause the system to hang due to file system metadata becoming unsynchronized. To prevent this issue from occurring in O_DIRECT_NO_FSYNC mode, InnoDB now calls fsync() after creating a new file, after increasing file size, and after closing a file. The fsync() system call is still skipped after each write operation.
With the changes described above, O_DIRECT_NO_FSYNC mode can now be safely used on EXT4 and XFS file systems.
InnoDB: An assertion was raised when attempting to write to a tablespace file greater than 4GB in size on a 64-bit Windows system. The failure was due to a narrowing cast.
Partitioning: Repeated ALTER TABLE statements on partitioned tables containing BLOB or TEXT columns were not always handled correctly.
Partitioning: ALTER TABLE ... EXCHANGE PARTITION did not work when the partitioned table had one or more partition definitions using the DATA DIRECTORY option. This fix supports partitioned tables using the InnoDB storage engine only.
Replication: A patch to correct the handling of quotes for identifiers in ROLLBACK TO SAVEPOINT statements in the binary log was not correctly applied to subsequent MySQL versions.
Replication: Following a patch in MySQL 5.7.23, LOAD DATA statements stopped statement-based replication from a MySQL 5.7.22 master to a replication slave at a later release. The problem has now been fixed.
Replication: In some circumstances, the CHANGE MASTER TO statement could not be used on a replication slave if the master info log had been changed from a table (master_info_repository=TABLE) into a file (master_info_repository=FILE).
Replication: When the system variables binlog_transaction_dependency_tracking and binlog_transaction_dependency_history_size were set or read, the types of lock that were required could result in a deadlock scenario, because the same locks were also required for working with the active binary logs. A new lock type is now used instead for access to the transaction dependency tracking system variables, so that this deadlock cannot occur.
Replication: The PURGE BINARY LOGS TO 'log_name' statement failed for binary log files that had been moved to another location using mysqlbinlogmove. Such files are still listed in the binary log index file, but they are listed using an absolute path, rather than a path relative to the directory where the binary log files are normally stored. MySQL Server can now locate and purge moved binary log files successfully.
Replication: If autocommit was set to 0 for a replication slave or Group Replication group member where GTIDs were in use and super_read_only=ON was set, server shutdown was prevented by a transaction that did not complete. The transaction was attempting to save GTIDs to the mysql.gtid_executed table, but the update failed because super_read_only=ON was set. (With autocommit set to 1, the transaction would complete in this situation, and the mysql.gtid_executed table would instead be updated at server startup.) Now, the check for the super_read_only setting is skipped for this task, so the transaction is able to save the GTIDs to the mysql.gtid_executed table and complete regardless of the combination of super_read_only and autocommit settings.
Replication: An assertion was raised in debug builds if an XA ROLLBACK statement was issued for an unknown transaction identifier when the gtid_next value had been set manually. The server now does not attempt to update the GTID state if an XA ROLLBACK statement fails with an error.
Replication: The value returned by a SHOW SLAVE STATUS statement for the total combined size of all existing relay log files (Relay_Log_Space) could become much larger than the actual disk space used by the relay log files. The I/O thread did not lock the variable while it updated the value, so the SQL thread could automatically delete a relay log file and write a reduced value before the I/O thread finished updating the value. The I/O thread then wrote its original size calculation, ignoring the SQL thread's update and so adding back the space for the deleted file. The Relay_Log_Space value is now locked during updates to prevent concurrent updates and ensure an accurate calculation.
Replication: If the relay log index file was temporarily locked for viewing by a backup process for a replication slave, and MySQL Server also attempted to access the file at that time for rename or delete operations, the backup completed with warnings, but MySQL Server experienced an unexpected halt. MySQL Server now retries the file access operation a number of times in case this or a similar scenario is the explanation and the file becomes available again before long.
Replication: With sync_binlog=1 set, if the binary log was rotated during a commit before the binary log end position was updated, replication stopped on the slave because the server attempted to use the old binary log end position with the new binary log file. The server now compares the binary log file name with the active binary log file when updating the binary log end position, so that the issue does not occur.
Replication: When adding a new member to a group, if the certification information was too big to transmit, an event was generated that caused failures in all group members. To avoid this situation, now if the certification information is too large an error is generated which makes the joining member leave the group.
Replication: When stopping replication, any channels that had pending transactions could cause a deadlock in Group Replication.
The keyring_aws plugin was missing from Commercial packages for macOS.
The supported macOS versions for this plugin now are macOS 10.13 and 10.14.
MySQL Enterprise Firewall did not work well if the audit_log plugin was installed.
The server permitted creation of databases with the same name as redo log files, which could result in unexpected server behavior. Such names are no longer permitted as database names.
Removal of Sun RPC and XDR from glibc into a separate libtirpc library caused problems with libasan on some platforms.
In LDAP group search filter values, special characters were not escaped. Special characters in the user DN now are escaped with their hexadecimal equivalant as follows:
* => \2a
( => \28
) => \29
\ => \5c
\0 => \00
A memory leak was caused by GET_LOCK() calls with a zero timeout that failed due to concurrent connections holding the same user-level lock.
mysqlpump did not free all allocated resources when it encountered an error, resulting in memory leaks.
For debug builds, the server could exit when attempting to roll back CREATE USER statements.
Mishandling of deprecated system variables could cause output from queries on the Performance Schema variables_by_thread table to be incorrect.
When a subquery contained a UNION, the count of the number of subquery columns was calculated incorrectly.
On a GTID-enabled server, concurrent statements on the INFORMATION_SCHEMA.COLUMNS table could deadlock.
Comparing log file names as strings using the memcmp() function resulted in uninitialized memory read errors. The comparison now uses the strncmp() function. Thanks to Zsolt Parragi and Laurynas Biveinis for their contributions.
The optimizer skipped the second column in a composite index when executing an inner join with a LIKE clause against the second column.
CREATE TABLE ... SELECT could create date columns with “zero” date default values when it should have created them without a default value.
The transformation of IN subquery predicates into semijoins was not handled correctly for a very large number of tables.
Server mishandling of SIGHUP signals could result in a server exit.
When the character set of one string comparison operand was a superset of the character set of the other operand, some comparisons were disallowed that should be permitted by converting the operand with the “smaller” character set to the “larger” character set. utf8mb4 and utf32 are considered to be a superset of any other encoding.
Improper memory handling by account management statements could result in server misbehavior.
Executing a prepared statement to do a multiple-row insert with large number of placeholders consumed excessive memory and could execute slowly.
The parser accepted invalid SET statement syntax in trigger definitions that could result in a server exit.
The server failed to start if the keyring_encrypted_file plugin keyring file was invalid.
Keyring migration failed with source and destination keyring plugins of keyring_okv and keyring_encrypted_file, respectively.
When executing a prepared statement with a procedure call with the CURSOR_TYPE_READ_ONLY flag set, the client library hung if the procedure performed a SELECT that returned an empty result set.
The parser performed some out-of-memory checks incorrectly.
When binlog_format is ROW or MIXED, operations on temporary tables are not logged. Previously, the exception to this rule was that when the connection was terminated at the end of the session, the statement DROP TEMPORARY TABLE IF EXISTS was logged for any temporary tables that had been opened in the session. For row-based replication, this behavior caused an unnecessary write to the binary log, and added a transaction sequence number for the GTID where these were enabled.
Now, when a temporary table is created in a session, the binary logging format is tracked. The DROP TEMPORARY TABLE IF EXISTS statement is only logged at the end of the session if statement-based format was in effect when the temporary table was created, so the CREATE TEMPORARY TABLE statement was logged. If row-based or mixed-format binary logging was in use when the table was created, the DROP TEMPORARY TABLE IF EXISTS statement is not logged.
Thanks to Laurynas Biveinis for the patch.
DML statements using IGNORE were not always handled correctly on tables having generated columns.
A query employing a dynamic range and an index merge could use more memory than expected.
2019-02-05 21:19:55 +01:00
|
|
|
CHECK_INTERPRETER_SKIP+= share/mysql/test/std_data/dtrace.d
|
2016-09-16 08:49:11 +02:00
|
|
|
|
Security Notes
* Security Fix: The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2l. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html.
This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead.
Platform-Specific Notes
* Linux: The generic Linux build for MySQL 5.6 is now built on Oracle Linux 6 using glibc 2.12. Systems that use the build need to have glibc 2.12 or later installed on them.
Functionality Added or Changed
* For Windows, MSI installer packages now include a check for the required Visual Studio redistributable package, and produce a message asking the user to install it if it is missing.
* The mysql client now supports a --binary-as-hex option that causes display of binary data using hexadecimal notation (0xvalue). Thanks to Daniël van Eeden for the patch.
* mysqlaccess now looks for its configuration file only in the SYSCONFDIR directory and /etc.
Bugs Fixed
* InnoDB: The server allocated memory unnecessarily for an operation that rebuilt the table.
* InnoDB: When using an index merge optimizer switch, a SELECT COUNT(*) operation sometimes returned 0. Partitioning code incorrectly performed a memcpy instead of a column copy of columns read by the index, causing the wrong records to be copied.
* Replication: A USE statement that followed a SET GTID_NEXT statement sometimes had no effect.
* Replication: If the binary log on a master server was rotated and a full disk condition occurred on the partition where the binary log file was being stored, the server could stop unexpectedly. The fix adds a check for the existence of the binary log when the dump thread switches to next binary log file. If the binary log is disabled, all binary logs up to the current active log are transmitted to slave and an error is returned to the receiver thread.
* Replication: If a relay log index file named relay log files that did not exist, RESET SLAVE ALL sometimes did not fully clean up properly.
* Replication: mysqlbinlog, if invoked with the --raw option, does not flush the output file until the process terminates. But if also invoked with the --stop-never option, the process never terminates, thus nothing is ever written to the output file. Now the output is flushed after each event.
* Replication: A memory leak in mysqlbinlog was fixed. The leak happened when processing fake rotate events, or when using --raw and the destination log file could not be created. The leak only occurred when processing events from a remote server. Thanks to Laurynas Biveinis for his contribution to fixing this bug.
* Replication: Multi-threaded slaves could not be configured with small queue sizes using slave_pending_jobs_size_max if they ever needed to process transactions larger than that size. Any packet larger than slave_pending_jobs_size_max was rejected with the error ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX, even if the packet was smaller than the limit set by slave_max_allowed_packet.
* With this fix, slave_pending_jobs_size_max becomes a soft limit rather than a hard limit. If the size of a packet exceeds slave_pending_jobs_size_max but is less than slave_max_allowed_packet, the transaction is held until all the slave workers have empty queues, and then processed. All subsequent transactions are held until the large transaction has been completed. The queue size for slave workers can therefore be limited while still allowing occasional larger transactions.
* mysqldump could write database names in USE statements incorrectly.
* If the mysql_stmt_close() C API function was called, it freed memory that later could be accessed if mysql_stmt_error(), mysql_stmt_errno(), or mysql_stmt_sqlstate() was called. To obtain error information after a call to mysql_stmt_close(), call mysql_error(), mysql_errno(), or mysql_sqlstate() instead.
* Queries could be cached incorrectly, leading to incorrect query results, under these circumstances: InnoDB table; rows are being inserted but have not yet been committed; a query uses the table as a base table in a derived table; the optimizer chooses to materialize the derived table.
* Man pages for a few utilities were missing from Debian/Ubuntu packages.
* The field-t unit test failed to run with AddressSanitizer enabled. Thanks to Laurynas Biveinis for the patch.
* Debian client packages were missing information about conflicts with native packages.
* The Perl path in #! lines at the beginning of Perl scripts has been adjusted to /usr/local/bin/perl for FreeBSD 11.
* The server exited abnormally attempting to access invalid memory.
* A race condition could occur for CREATE TABLE statements with DATA DIRECTORY or INDEX DIRECTORY clauses.
* MySQL compilation in different directories produced different builds to leakage of absolute paths into debug information and __FILE__.
* mysqld_failed to start the server if the --datadir option was specified with a relative path name.
* With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users was permitted under certain conditions.
*Certain stored functions, if used in a query WHERE clause, could be handled using Index Condition Pushdown (which should not happen), resulting in a server exit.
* On x86 machines, the uint3korr() macro read 4 bytes of data instead of the intended 3 bytes.
* An assertion was raised during a fetch operation by the memcached plugin.
* Queries that contained UNION in a subquery and GROUP BY could return incorrect results.
* LOAD XML INFILE performance became noticeably slower when the XML file being read contained a great many spaces, such as those introduced by indenting or pretty-printing. Now all leading whitespace is trimmed from each such value before reading it into memory.
2017-07-20 18:41:10 +02:00
|
|
|
SUBST_CLASSES+= perlpath
|
|
|
|
|
SUBST_STAGE.perlpath= pre-configure
|
|
|
|
|
SUBST_MESSAGE.perlpath= Fixing Perl paths.
|
|
|
|
|
SUBST_FILES.perlpath= scripts/mysql_config.pl.in
|
|
|
|
|
SUBST_FILES.perlpath+= scripts/mysqld_multi.sh
|
|
|
|
|
SUBST_FILES.perlpath+= scripts/mysqldumpslow.sh
|
|
|
|
|
SUBST_SED.perlpath= -e 's,@PERL_PATH@,${PERL5},g'
|
|
|
|
|
|
2016-09-16 08:49:11 +02:00
|
|
|
INSTALLATION_DIRS+= bin
|
mysql57: updated to 5.7.24
Changes in MySQL 5.7.24
Deprecation and Removal Notes
* InnoDB; Partitioning: Support for placing table partitions in shared tablespaces is deprecated and will be removed in a future version of MySQL. Shared tablespaces include the system tablespace and general tablespaces. For information about identifying partitions in shared tablespaces and moving them to file-per-table tablespaces, see Preparing Your Installation for Upgrade.
* InnoDB: Support for TABLESPACE = innodb_file_per_table and TABLESPACE = innodb_temporary clauses with CREATE TEMPORARY TABLE is deprecated and will be removed in a future MySQL version.
Functionality Added or Changed
Replication: Use the group_replication_exit_state_action option to configure how Group Replication behaves when a member leaves the group involuntarily, for example when it is expelled from the group due to an unstable network connection. When group_replication_exit_state_action is set to ABORT_SERVER, upon exiting the group unintentionally, the instance shuts MySQL down, and when group_replication_exit_state_action is set to READ_ONLY the instance sets MySQL to super read only mode instead and its state is set to ERROR.
Previously, file I/O performed in the I/O cache in the mysys library was not instrumented, affecting in particular file I/O statistics reported by the Performance Schema about the binary log index file. Now, this I/O is instrumented and Performance Schema statistics are accurate. Thanks to Yura Sorokin for the contribution.
The zlib library version bundled with MySQL was raised from version 1.2.3 to version 1.2.11. MySQL implements compression with the help of the zlib library.
The zlib compressBound() function in zlib 1.2.11 returns a slightly higher estimate of the buffer size required to compress a given length of bytes than it did in zlib version 1.2.3. The compressBound() function is called by InnoDB functions that determine the maximum row size permitted when creating compressed InnoDB tables or inserting rows into compressed InnoDB tables. As a result, CREATE TABLE ... ROW_FORMAT=COMPRESSED or INSERT operations with row sizes very close to the maximum row size that were successful in earlier releases could now fail.
Bugs Fixed
* InnoDB: An ALTER TABLE operation that added a primary key produced a segmentation fault.
* InnoDB: A query that scanned the primary key of a table did not return the expected result.
* InnoDB: A query interruption during a lock wait caused an error.
* InnoDB: An index record was not found when updating a secondary index defined on a generated column.
* InnoDB: The update log applied as part of an online ALTER TABLE operation did not take into account the computed value of the generated column in the old row while updating the secondary index.
* InnoDB: An unsupported DDL operation involving a foreign key constraint raised an assertion.
* InnoDB: An attempted foreign key check on a discarded table caused a segmentation fault.
* InnoDB: An assertion was raised during an OPTIMIZE TABLE operation.
* InnoDB: A foreign key constraint name was duplicated during a rename table operation, causing a failure during later query execution.
* InnoDB: In a function called before the execution of a statement in a stored procedure, a read and write operation on trx->lock.start_stmt was not protected by a mutex.
* InnoDB: An error occurred during a DDL operation due to a mismatch in a REDUNDANT row format calculation that determines the length of the online log.
* InnoDB: The location of the Innodb Merge Temp File that reported by the wait/io/file/innodb/innodb_temp_file Performance Schema instrument was incorrect.
* Partitioning: When a CREATE TABLE ... PARTITION BY ... statement failed due to an invalid partition definition, the server did not remove any partition files which might have been created prior to encountering the invalid PARTITION clause.
* Partitioning: It was possible to perform FLUSH TABLES FOR EXPORT on a partitioned table created with innodb_file_per_table=1 after discarding its tablespace. Attempting to do so now raises ER_TABLESPACE_DISCARDED.
* Replication: When the binlog_group_commit_sync_delay system variable is set to a wait time to delay synchronization of transactions to disk, and the binlog_group_commit_sync_no_delay_count system variable is also set to a number of transactions, the MySQL server exits the wait procedure if the specified number of transactions is reached before the specified wait time is reached. The server manages this process by checking on the transaction count after a delta of one tenth of the time specified by binlog_group_commit_sync_delay has elapsed, then subtracting that interval from the remaining wait time.
more...
2018-11-22 17:14:53 +01:00
|
|
|
TEST_TARGET= test
|
2016-09-16 08:49:11 +02:00
|
|
|
|
|
|
|
|
.include "../../mk/compiler.mk"
|
|
|
|
|
|
|
|
|
|
.if !empty(PKGSRC_COMPILER:Msunpro)
|
|
|
|
|
CFLAGS+= -D_POSIX_C_SOURCE=199506L -D__EXTENSIONS__
|
|
|
|
|
CXXFLAGS+= -D_POSIX_C_SOURCE=199506L -D__EXTENSIONS__
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.include "../../archivers/lz4/buildlink3.mk"
|
|
|
|
|
BUILDLINK_AUTO_DIRS.mysql-client= no
|
|
|
|
|
.include "../../databases/mysql57-client/buildlink3.mk"
|
|
|
|
|
.include "../../security/tcp_wrappers/buildlink3.mk"
|
|
|
|
|
.include "../../mk/bsd.pkg.mk"
|
