summaryrefslogtreecommitdiff
path: root/databases/mysql51-server
AgeCommit message (Collapse)AuthorFilesLines
2012-03-09Fix build on a mix of GNU/Sun tools.fhajny2-1/+16
2012-01-23Really bump PKGREVISIONsbd1-1/+2
2012-01-23readline isn't just a build dependency, if 'ndb_mgm' is built it has asbd1-5/+7
full dependency on readline. Bump PKGREVISION
2012-01-12Changes 5.1.61:adam2-5/+12
* InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction. * An incorrect InnoDB assertion could cause the server to halt. This issue only affected debug builds. The assertion referenced the source file btr0pcur.ic and the variable cursor->pos_state. * The handle_segfault() signal-handler code in mysqld could itself crash due to calling unsafe functions. * ARCHIVE tables with NULL columns could cause server crashes or become corrupt under concurrent load. * Enabling myisam_use_mmap could cause the server to crash. * Concurrent access to ARCHIVE tables could cause corruption.
2011-12-02Changes 5.1.60:adam2-5/+19
* Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * 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. Bugs Fixed * Important Change: 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: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * 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.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
2011-09-12Add proper upper limit to not result in mix of MySQL 5.1 and 5.5joerg1-2/+2
2011-08-02Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58).taca2-26/+31
This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-05-08Update mysql51-{client,server} package to 5.1.57.taca3-19/+19
This is simply maintenance release, no security fix. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in detail.
2011-03-19Fix broken patch. The files to patch must not include the name of thejmmv2-5/+5
work directory.
2011-03-17Fix building with Clang.adam3-4/+36
2011-03-08Update MySQL package to 5.1.56.taca6-98/+18
Functionality added or changed: * mysqldump --xml now displays comments from column definitions. (Bug #13618) Bugs fixed: * InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É in the query plan that were higher than expected. NULL values were treated in an inconsistent way. The inaccurate statistics could trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE setting, because the queries did not really examine as many rows as reported. (Bug #30423) * Partitioning: Trying to use the same column more than once in the partitioning key when partitioning a table by KEY caused mysqld to crash. Such duplication of key columns is now expressly disallowed, and fails with an appropriate error. (Bug #53354, Bug #57924) * Replication: When using the statement-based logging format, INSERT ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting transactional tables that did not fail were not written to the binary log if they did not insert any rows. (With statement-based logging, all successful statements should be logged, whether they do or do not cause any rows to be changed.) (Bug #59338) * Replication: Formerly, STOP SLAVE stopped the slave I/O thread first and then stopped the slave SQL thread; thus, it was possible for the I/O thread to stop after replicating only part of a transaction which the SQL thread was executing, in wich case¡½if the transaction could not be rolled back safely¡½the SQL thread could hang. Now, STOP SLAVE stops the slave SQL thread first and then stops the I/O thread; this guarantees that the I/O thread can fetch any remaining events in the transaction that the SQL thread is executing, so that the SQL thread can finish the transaction if it cannot be rolled back safely. (Bug #58546) * A query of the following form returned an incorrect result, where the values for col_name in the result set were entirely replaced with NULL values: SELECT DISTINCT col_name ... ORDER BY col_name DESC; (Bug #59308, Bug #11766241) * DELETE or UPDATE statements could fail if they used DATE or DATETIME values with a year, month, or day part of zero. (Bug #59173) * The ESCAPE clause for the LIKE operator allows only expressions that evaluate to a constant at execution time, but aggregrate functions were not being rejected. (Bug #59149) * Memory leaks detected by Valgrind, some of which could cause incorrect query results, were corrected. (Bug #59110, Bug #11766075) mysqlslap failed to check for a NULL return from mysql_store_result() and crashed trying to process the result set. (Bug #59109) * In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could cause a server crash. (Bug #58371) * When mysqldadmin was run with the --sleep and --count options, it went into an infinite loop executing the specified command. (Bug #58221) * Some string manipulating SQL functions use a shared string object intended to contain an immutable empty string. This object was used by the SQL function SUBSTRING_INDEX() to return an empty string when one argument was of the wrong datatype. If the string object was then modified by the SQL function INSERT(), undefined behavior ensued. (Bug #58165, Bug #11765225) * Parsing nested regular expressions could lead to recursion resulting in a stack overflow crash. (Bug #58026, Bug #11765099) * The mysql client went into an infinite loop if the standard input was a directory. (Bug #57450) * The expression const1 BETWEEN const2 AND field was optimized incorrectly and produced incorrect results. (Bug #57030, Bug #11764215) * Some RPM installation scripts used a hardcoded value for the data directory, which could result in a failed installation for users who have a nonstandard data directory location. The same was true for other configuration values such as the PID file name. (Bug #56581, Bug #11763817) * On FreeBSD and OpenBSD, the server incorrectly checked the range of the system date, causing legal values to be rejected. (Bug #55755, Bug #11763089) * When using ExtractValue() or UpdateXML(), if the XML to be read contained an incomplete XML comment, MySQL read beyond the end of the XML string when processing, leading to a crash of the server. (Bug #44332)
2011-02-13Update mysql51-{client,server} package to 5.1.55.taca2-53/+83
Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html MySQL 5.1.55 Functionality added or changed: The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug#40230)
2010-12-16Update mysql51-{client,server} package to 5.1.54.taca3-16/+20
Functionality added or changed: * Support for the IBMDB2I storage engine has been removed. (Bug#58079) * The pstack library was nonfunctional and has been removed, along with the --with-pstack option for configure. The --enable-pstack option for mysqld is deprecated and will be removed in MySQL 5.5. (Bug#57210) Bugs fixed: * Performance: InnoDB Storage Engine: Improved concurrency when several ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for InnoDB tables. (Bug#53046) * InnoDB Storage Engine: For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#57799) * Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0 statement on an AUTO_INCREMENT column caused the debug server to crash. (Bug#57890) * Several compilation problems were fixed. (Bug#57992, Bug#57993, Bug#57994, Bug#57995, Bug#57996, Bug#57997, Bug#58057) * Passing a string that was not null-terminated to UpdateXML() or ExtractValue() caused the server to fail with an assertion. (Bug#57279) * Queries executed using the Index Merge access method and a temporary file could return incorrect results. (Bug#56862) * The find_files() function used by SHOW statements performed redundant and unnecessary memory allocation. (Bug#51208)
2010-11-26Update mysql51-{client,server} to 5.1.53.taca2-6/+27
Most changes are related to replication and seems to no security fix. For more detail, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html
2010-11-14Removed MAKE_JOBS_SAFE=no; compiles fine with MAKE_JOBS=8 on NetBSD and MacOSXadam1-3/+1
2010-11-04Update mysql51-{client,server} package from 5.1.51 to 5.1.52.taca2-5/+18
This is maintainous release and pleare refer in detail: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html One note from the changes: * Security Fix: In prepared-statement mode, EXPLAIN for a SELECT from a derived table caused a server crash. (Bug#54488)
2010-10-06Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51.taca3-10/+22
For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-09-08Update mysql51-{client,server} to 5.1.50.taca3-7/+18
Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-50.html for full changes . InnoDB Notes: InnoDB Plugin has been upgraded to version 1.0.11. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages, and any builds produced with the icc compiler. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: Important Change: Replication: The LOAD DATA INFILE statement is now considered unsafe for statement-based replication. When using statement-based logging mode, the statement now produces a warning; when using mixed-format logging, the statement is made using the row-based format. (Bug#34283) Partitioning: UPDATE and INSERT statements affecting partitioned tables performed poorly when using row-based replication. (Bug#52517) Partitioning: INSERT ON DUPLICATE KEY UPDATE statements performed poorly on tables having many partitions. This was because the handler function for reading a row from a specific index was not optimized in the partitioning handler. (Bug#52455) The server could crash on shutdown, if started with --innodb-use-system-malloc=0. (Bug#55581) GROUP BY operations used max_sort_length inconsistently. (Bug#55188) Building MySQL on Solaris 8 x86 failed when using Sun Studio due to gcc inline assembler code. (Bug#55061) In debug builds, an assertion could be raised when the server tried to send an OK packet to the client after having failed to detect errors during processing of the WHERE condition of an UPDATE statement. (Bug#54734) The database server could crash when renaming a table that had active transactions. (This issue only affected the database server when built for debugging.) (Bug#54453) The server could crash during the recovery phase of startup, if it previously crashed while inserting BLOB or other large columns that use off-page storage into an InnoDB table created with ROW_FORMAT=REDUNDANT or ROW_FORMAT=COMPACT. (Bug#54408) For an InnoDB table created with ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ UNCOMMITTED isolation level could cause the server to stop with an assertion error, if BLOB or other large columns that use off-page storage were being inserted at the same time. (Bug#54358) A client could supply data in chunks to a prepared statement parameter other than of type TEXT or BLOB using the mysql_stmt_send_long_data() C API function (or COM_STMT_SEND_LONG_DATA command). This led to a crash because other data types are not valid for long data. (Bug#54041) mysql_secure_installation did not properly identify local accounts and could incorrectly remove nonlocal root accounts. (Bug#54004) Transactions could be incorrectly committed during recovery, rather than rolled back, if the server crashed and was restarted after performing ALTER TABLE...ADD PRIMARY KEY on an InnoDB table, or some other operation that involves copying the entire table. (Bug#53756) Portability problems in SHOW STATUS could lead to incorrect results on some platforms. (Bug#53493) Builds of MySQL generated a large number of warnings. (Bug#53445) With lower_case_table_names set to a nonzero value, searches for table or database names in INFORMATION_SCHEMA tables could produce incorrect results. (Bug#53095) The ABI check for MySQL failed to compile with gcc 4.5. (Bug#52514) mysql_secure_installation sometimes failed to locate the mysql client. (Bug#52274) Reading a ucs2 data file with LOAD DATA INFILE was subject to three problems. 1) Incorrect parsing of the file as ucs2 data, resulting in incorrect length of the parsed string. This is fixed by truncating the invalid trailing bytes (incomplete multibyte characters) when reading from the file. 2) Reads from a proper ucs2 file did not recognize newline characters. This is fixed by first checking whether a byte is a newline (or any other special character) before reading it as a part of a multibyte character. 3) When using user variables to hold column data, the character set of the user variable was set incorrectly to the database charset. This is fixed by setting it to the character set specified in the LOAD DATA INFILE statement, if any. (Bug#51876) Searches in INFORMATION_SCHEMA tables for rows matching a nonexistent database produced an error instead of an empty query result. (Bug#49542) On FreeBSD, memory mapping for MERGE tables could fail if underlying tables were empty. (Bug#47139) The my_like_range_xxx() functions returned badly formed maximum strings for Asian character sets, which caused problems for storage engines. (Bug#45012) A debugging assertion could be raised after a write failure to a closed socket. (Bug#42496) An assertion failure occurred within yaSSL for very long keys. (Bug#29784) See also Bug#53463.
2010-08-13Fix some my_time_t (long) v.s. time_t problem introduced MySQL 5.1.49.taca7-6/+109
This problem results mysqld to exit on start up. 5.1/i386 5.1/amd64 5.99.38/i386 5.99.38/amd64 my_time_t int32_t int64_t int32_t int64_t time_t int32_t int32_t int64_t int64_t I confirmed to mysqld running on these four case except 5.99.38/i386. Bump PKG_REVISION.
2010-08-11Update mysql51-client and mysql51-server to 5.1.49.taca5-68/+199
Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-07-05Update mysql51-{client,server} package to 5.1.48.taca2-10/+35
Secunia Advisory SA40333 (http://secunia.com/advisories/40333/) reports that this release fixes DoS problem and it refers: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html http://bugs.mysql.com/bug.php?id=53804 But news-5-1-48.html dosen't contains about bug id 53804... Anyway, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-48.html for full changes.
2010-05-26Update mysql51-{client,server} package to 5.1.47.taca3-93/+86
For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html. Here is important changes: InnoDB Plugin Notes: * InnoDB Plugin has been upgraded to version 1.0.8. This version is considered of General Availability (GA) quality. InnoDB Plugin Change History, may contain information in addition to those changes reported here. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Functionality added or changed: * InnoDB stores redo log records in a hash table during recovery. On 64-bit systems, this hash table was 1/8 of the buffer pool size. To reduce memory usage, the dimension of the hash table was reduced to 1/64 of the buffer pool size (or 1/128 on 32-bit systems). (Bug#53122) Security fixed: * Security Fix: The server failed to check the table name argument of a COM_FIELD_LIST command packet for validity and compliance to acceptable table name standards. This could be exploited to bypass almost all forms of checks for privileges and table-level grants by providing a specially crafted table name argument to COM_FIELD_LIST. In MySQL 5.0 and above, this allowed an authenticated user with SELECT privileges on one table to obtain the field definitions of any table in all other databases and potentially of other MySQL instances accessible from the server's file system. Additionally, for MySQL version 5.1 and above, an authenticated user with DELETE or SELECT privileges on one table could delete or read content from any other table in all databases on this server, and potentially of other MySQL instances accessible from the server's file system. (Bug#53371, CVE-2010-1848) * Security Fix: The server was susceptible to a buffer-overflow attack due to a failure to perform bounds checking on the table name argument of a COM_FIELD_LIST command packet. By sending long data for the table name, a buffer is overflown, which could be exploited by an authenticated user to inject malicious code. (Bug#53237, CVE-2010-1850) * Security Fix: The server could be tricked into reading packets indefinitely if it received a packet larger than the maximum size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-08Fix build on DragonFly by removing DragonFly-specific patch.wiz2-15/+1
From Alexander Polakov in PR 43280.
2010-04-24Update mysql51-client/mysql51-server package to 5.1.46.taca4-22/+951
This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-20Update mysql51-client/mysql51-server package to 5.1.45.taca4-9/+35
This is maintainous release and please refer for full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html Added a patch for recent security problem to mysql51-server, too. http://secunia.com/advisories/39454
2010-03-21Add mysqlmanager, ndb-cluster and pstack PKG_OPTIONS.taca6-14/+130
These are control some optional functions for mysql51-server (leaf package). Bump PKGREVISION.
2010-03-17Add buildlink3.mk file.wiz1-0/+15
2010-03-16Enable PIC compilation, needed for working mysql-embedded supportwiz2-2/+4
(and perhaps also on Solaris). Bump PKGREVISION. Ok taca@
2010-03-04Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 includingtaca28-0/+4411
embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most 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).