summaryrefslogtreecommitdiff
path: root/databases/mysql55-server/Makefile
AgeCommit message (Collapse)AuthorFilesLines
2016-04-18Changes 5.5.49:adam1-2/+1
Security Notes -------------- MySQL client programs now support an --ssl-mode option that enables you to specify the security state of the connection to the server. The default value is DISABLED (establish an unencrypted connection). --ssl-mode=REQUIRED) can be specified to require a secure connection, or fail if a secure connection cannot be obtained. These clients support --ssl-mode: mysql, mysqladmin, mysqlcheck, mysqldump, mysqlimport, mysqlshow, mysqlpump, mysqlslap, mysqltest, mysql_upgrade. For more information, see Command Options for Secure Connections. Bugs Fixed
2016-03-05Bump PKGREVISION for security/openssl ABI bump.jperkin1-1/+2
2015-04-08Changes 5.5.43:adam1-2/+1
* CMake support was updated to handle CMake version 3.1. * The server now includes its version number when it writes the initial “starting” message to the error log, to make it easier to tell which server instance error log output applies to. This value is the same as that available from the version system variable. * Bug fixes.
2015-03-22The bundled SMF manifest should not have a project called for. This had beenfhajny1-2/+2
added erroneously, based on modified Joyent manifests. Bump PKGREVISION for the MySQL cluster/server packages.
2015-02-07Fix MESSAGE_SRC for the sphinx option. Bump PKGREVISION.fhajny1-1/+2
2015-02-07Changes 5.5.42:adam1-2/+1
* Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they provide weak encryption. * yaSSL was upgraded to version 2.3.7. * The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. * Bugs Fixed
2014-12-05Pipe mysqld_safe's stdout and stderr to syslog to avoid the problemschmonz1-1/+2
in PR pkg/48271. (There's a mysqld_safe switch to log to syslog, which would also work around the problem, at the expense mutually exclusivity with normal MySQL logging). Bump PKGREVISIONs.
2014-10-09Remove SVR4_PKGNAME, per discussion on tech-pkg.wiz1-2/+1
2014-08-10Changes 5.5.39:adam1-1/+4
CMake support was updated to handle CMake version 3. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed InnoDB: Opening a parent table that has thousands of child tables could result in a long semaphore wait condition. Partitioning: Selecting from a table having multiple columns in its primary key and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column listed in the primary key definition, returned an incorrect result. Replication: When using row-based replication, updating or deleting a row on the master that did not exist on the slave led to failure of the slave when it tried to process the change. This problem occurred with InnoDB tables lacking a primary key. Replication: Quotation marks were not always handled correctly by LOAD DATA INFILE when written into the binary log. Replication: A group of threads involved in acquiring locks could deadlock when the following events occurred: Dump thread reconnects from slave; on master, a new dump thread tries to kill zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to acquire LOCK_log. Application thread executing show binary logs, having acquired LOCK_log and about to acquire LOCK_index. Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it is about to acquire LOCK_thread_count. Application thread executing SHOW PROCESSLIST (or SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to acquire the zombie dump thread's LOCK_thd_data.
2014-06-14fix SMF Manifest installation by not overwriting INSTALLATION_DIRSwiedi1-2/+2
2014-04-14Don't hardcode PID file. Instead, give the user the option to set it. Therodent1-1/+2
rc.d script overrides my.cnf directives. Hardcoding the PID can cause a problem on systems transitioning to MySQL packages from pkgsrc.
2014-03-31Changes 5.5.37:adam1-2/+1
Functionality Added or Changed On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. Bugs Fixed InnoDB: A regression introduced by Bug 14329288 would result in a performance degradation when a compressed table does not fit into memory. InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000 microseconds. The previous maximum value (4294967295 microseconds on 32-bit and 18446744073709551615 microseconds on 64-bit) was unnecessarily large. Because the maximum value of innodb_thread_sleep_delay is limited by the value set for innodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximum value for innodb_thread_sleep_delay is now the same as the maximum value for innodb_adaptive_max_sleep_delay. InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion. InnoDB: InnoDB would fail to start when innodb_data_file_path specified the data file size in kilobytes by appending K to the size value. InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs. InnoDB: Assertion failure in thread thread_num in file ibuf0ibuf.cc line 4080 InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page)) InnoDB: Decreasing the auto_increment_increment value would have no affect on the next auto-increment value. Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication. Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead. Replication: Statements involving the Performance Schema tables should not be written to the binary log, because the content of these tables is applicable only to a given MySQL Server instance, and may differ greatly between different servers in a replication topology. The database administrator should be able to configure (INSERT, UPDATE, or DELETE) or flush (TRUNCATE TABLE) performance schema tables on a single server without affecting others. However, when replicating from a MySQL 5.5 master to a MySQL 5.5 or later slave, warnings about unsafe statements updating Performance Schema tables were elevated to errors. For MySQL 5.6 and later slaves, this prevented the simultaneous use of performance_schema and GTIDs (see Replication with Global Transaction Identifiers, in the MySQL 5.6 Manual). This fix causes all updates on tables in the performance_schema database to be filtered on the master and not replicated, regardless of the type of logging that is in effect. Prior to this fix, statements using were handled by being marked as unsafe for replication, which caused warnings during execution; the statements were nonetheless written to the binary log, regardless of the logging format in effect. Existing replication behavior for tables in the INFORMATION_SCHEMA database is not changed by this fix. For more information, see MySQL Performance Schema. Compilation failed if MySQL was configured with CFLAGS set to include a -Werror option with an argument. A shared libmysqld embedded server library was not built on Linux. While printing the server version, the mysql client did not check for buffer overflow in a string variable. Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights. DROP TRIGGER succeeded even with the read_only system variable enabled. Updating the Performance Schema setup_instruments table on a replication master caused a slave to exit. Due to a race condition, it was possible for two threads to end up with the same query ID for different queries. When run by root, mysqld --help --verbose exited with a nonzero error code after displaying the help message. MySQL client programs from a Community Edition distribution could not connect using SSL to a MySQL server from an Enterprise Edition. This was due to a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing. A deadlock error occurring during subquery execution could cause an assertion to be raised. The Performance Schema stage/sql/Waiting to get readlock instrument is no longer used and has been removed. For system variables that take a string value, SET statements permitted an unquoted value, but values that contained dots were parsed incorrectly and only part of the value was assigned. For example, SET GLOBAL slow_query_log_file = my_slow.log assigned the value my_slow. Now such values must be quoted or an error occurs. On Windows, mysql_install_db.pl could be run only from within the bin directory under the installation directory.
2014-03-11Import initial SMF support for individual packages.jperkin1-1/+3
2014-02-12Recursive PKGREVISION bump for OpenSSL API version bump.tron1-1/+2
2013-12-05Remove CONFLICTS with ${PKGBASE}, these are automatic.wiz1-2/+2
Avoids unnecessary pkgin warning.
2013-12-03Changes 5.5.35:adam1-2/+1
* Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * Attempts to use the thread_concurrency system variable (which has an effect only for Solaris 8 and earlier) now indicate that it has no effect when that is the case. * Bugs Fixed
2013-07-31Changes 5.5.33:adam1-2/+1
* Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * comp_err now checks to make sure that new errors are not being added to MySQL 5.1 or 5.5 because the set of errors for these series is frozen. * Bugs Fixed
2013-07-17Distfile got changed (licence clause in mans). Revision bump.adam1-3/+2
Don't use mk/readline.buildlink3.mk! Must be devel/readline/buildlink3.mk!
2013-07-12Bump PKGREVISION of all packages which create users, to pick up change ofjperkin1-1/+2
sysutils/user_* packages.
2013-06-04Changes 5.5.32:adam1-2/+3
* mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
2013-05-20Do not poison build flags with mysql-client bl3 dirs.fhajny1-1/+2
2013-05-20Rely on mysql{55,56}-client's bl3 to restrict the dependency of serverfhajny1-5/+3
on client. Fixes situations where a binary mysql55-server package picks up mysql56-client as the best dependency because of the missing upper limit. Bump PKGREVISION.
2013-04-01Define INSTALL_INFODIR for cmake.sbd1-1/+2
2013-02-12Changes 5.5.30:adam1-2/+1
Refer to http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-30.html
2013-02-06PKGREVISION bumps for the security/openssl 1.0.1d update.jperkin1-1/+2
2011-10-22Changes 5.5.17:adam1-2/+1
* Replication: Previously, replication slaves could connect to the master server only through master accounts that use native authentication. Now replication slaves can also connect through master accounts that use nonnative authentication (except Windows native authentication) if the required client-side plugin is installed on the slave side in the directory named by the slave plugin_dir system variable. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Internal conversion of zero to binary and back could yield a result with incorrect precision. * Valgrind warnings generated by filesort operations were fixed. * mysqld_safe did not properly check for an already running instance of mysqld. * The help message for mysql_install_db did not indicate that it supports the --defaults-file, --defaults-extra-file and --no-defaults options. * An assertion designed to detect zero-length sort keys also was raised when the entire key set fit in memory. * myisampack could create corrupt FULLTEXT indexes when compressing tables. * A linking problem prevented the FEDERATED storage engine plugin from loading.
2011-09-17Only make "readlink" a run-time dependence if we are actually buildingtron1-1/+5
the embedded server which is the only binary that requires the library. No revision bump as there is no changed to the default binary package.
2011-09-17Change "readline" to a run-time dependence as it is used by at leasttron1-6/+2
"bin/mysql_embedded". This fixes the build in pkgsrc developer mode. Bump package revision because the dependence changed.
2011-07-08Changes 5.5.14:adam1-2/+2
* CMake configuration support on Linux now provides a boolean ENABLE_GCOV option to control whether to include support for gcov. * InnoDB now permits concurrent reads while creating a secondary index. * Client programs now display more information for SSL errors to aid in diagnosis and debugging of connection problems. * In the audit plugin interface, the event_class member was removed from the mysql_event_general structure and the calling sequence for the notification function changed. Originally, the second argument was a pointer to the event structure. The function now receives this information as two arguments: an event class number and a pointer to the event. Corresponding to these changes, MYSQL_AUDIT_INTERFACE_VERSION was increased to 0x0300. * The plugin_audit.h header file, and the NULL_AUDIT example plugin in the plugin/audit_null directory have been modified per these changes. See Section 21.2.4.7, “Writing Audit Plugins”. * Bug fixes.
2011-05-06Fix build on (at least RHEL 5.6). Tested (and no change) on NetBSD 5.99.51abs1-2/+6
2011-04-25MySQL is a SQL (Structured Query Language) database server. SQL is the mostadam1-0/+77
popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-19 22:07:55 +0000