Next | Query returned 74 messages, browsing 41 to 50 | Previous

History of commit frequency

CVS Commit History:


   2015-06-01 10:15:05 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
Changes 5.6.25:
Functionality Added or Changed
* MySQL Enterprise Firewall operates on parser states and does not work well \ 
together with the query cache, which circumvents the parser. MySQL Enterprise \ 
Firewall now checks whether the query cache is enabled. If so, it displays a \ 
message that the query cache must be disabled and does not load.

* my_print_defaults now masks passwords. To display passwords in cleartext, use \ 
the new --show option.

* MySQL distributions now include an innodb_stress suite of test cases. Thanks \ 
to Mark Callaghan for the contribution.

Bugs Fixed
* InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES \ 
table now shows the correct table creation time for partitioned InnoDB tables. \ 
The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the \ 
correct partition creation time for a partition of partitioned InnoDB tables.

The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a \ 
partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The \ 
UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a \ 
partition of a partitioned InnoDB table was last updated.

* InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions \ 
holding explicit locks.

* InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, \ 
strict_innodb, and strict_crc32) caused the server to halt when a non-matching \ 
checksum was encountered, even though the non-matching checksum was valid. For \ 
example, with innodb_checksum_algorithm=strict_crc32, encountering a valid \ 
innodb checksum caused the server to halt. Instead of halting the server, a \ 
message is now printed to the error log and the page is accepted as valid if it \ 
matches an innodb, crc32 or none checksum.

* InnoDB: The memcached set command permitted a negative expire time value. \ 
Expire time is stored internally as an unsigned integer. A negative value would \ 
be converted to a large number and accepted. The maximum expire time value is \ 
now restricted to INT_MAX32 to prevent negative expire time values.

* InnoDB: Removal of a foreign key object from the data dictionary cache during \ 
error handling caused the server to exit.

* InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and \ 
signal count values due to a counter overflow error.

* InnoDB: Failure to check the status of a cursor transaction read-only option \ 
before reusing the cursor transaction for a write operation resulted in a server \ 
exit during a memcached workload.

* InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup \ 
FLUSH TABLES WITH READ LOCK operation to hang.

* InnoDB: Estimates that were too low for the size of merge chunks in the result \ 
sorting algorithm caused a server exit.

* InnoDB: For full-text searches, the optimizer could choose an index that does \ 
not produce correct relevancy rankings.

* Partitioning: When creating a partitioned table, partition-level DATA \ 
DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of \ 
characters were handled incorrectly.

* Partitioning: Executing an ALTER TABLE on a partitioned table on which a write \ 
lock was in effect could cause subsequent SQL statements on this table to fail.

* Replication: When binary logging was enabled, using stored functions and \ 
triggers resulting in a long running procedure that inserted many records caused \ 
the memory use to increase rapidly. This was due to memory being allocated per \ 
variable. The fix ensures that in such a situation, memory is allocated once and \ 
the same memory is reused.

* Replication: If an error was encountered while adding a GTID to the received \ 
GTID set, the log lock was not being correctly released. This could cause a \ 
deadlock.

more...
   2015-04-08 12:38:48 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
Changes 5.6.24:
* 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.
* ALTER TABLE did not take advantage of fast alterations that might otherwise \ 
apply to the operation to be performed, if the table contained temporal columns \ 
found to be in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without \ 
support for fractional seconds precision).
* Statement digesting as done previously by the Performance Schema is now done \ 
at the SQL level regardless of whether the Performance Schema is compiled in and \ 
is available to other aspects of server operation that could benefit from it. \ 
The default space available for digesting is 1024 bytes, but can be changed at \ 
server startup using the max_digest_length system variable.
* Bug fixes.
   2015-03-22 08:44:44 by Filip Hajny | Files touched by this commit (8)
Log message:
The bundled SMF manifest should not have a project called for. This had been
added erroneously, based on modified Joyent manifests. Bump PKGREVISION for
the MySQL cluster/server packages.
   2015-02-07 20:23:41 by Adam Ciarcinski | Files touched by this commit (5) | Package updated
Log message:
Changes 5.6.23:
* The linked OpenSSL library for the MySQL Commercial Server has been updated \ 
from version 1.0.1j to version 1.0.1k.
* 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
   2015-02-07 17:04:47 by Filip Hajny | Files touched by this commit (4)
Log message:
Fix MESSAGE_SRC for the sphinx option. Bump PKGREVISION.
   2014-12-05 18:22:16 by Amitai Schlair | Files touched by this commit (6)
Log message:
Pipe mysqld_safe's stdout and stderr to syslog to avoid the problem
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-12-02 13:40:09 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
Changes 5.6.22:
* Noisy compiler warnings on FreeBSD 10 were silenced.
* CMake workarounds for older Mac OS X and XCode versions were removed. On Mac \ 
OS X, compilation always uses Clang, even for 32-bit builds.
* Previously, the MYSQL_MAINTAINER_MODE CMake option was turned on by default \ 
for debug builds and off for release builds, and MYSQL_MAINTAINER_MODE caused \ 
-Werror to be enabled when building with GCC. This made it cumbersome to enable \ 
-Werror under certain conditions, such as when compiling with Clang.
* Build support was modified to produce the same warnings for Clang as for gcc.
* CMake configuration for the Clang compiler sets more appropriate flags for \ 
building on Linux. Specifically, -g -fno-omit-frame-pointer -fno-strict-aliasing \ 
is now added.
* Bugs fixed.
   2014-10-17 19:07:45 by Filip Hajny | Files touched by this commit (8)
Log message:
Add optional Sphinx SE plugin support to MySQL 5.5 and 5.6.
Intented as a clean implementation (replacement) of wip/mysql-sphinxse.

SphinxSE is MySQL storage engine which can be compiled into MySQL server 5.x
using its pluggable architecture. Despite the name, SphinxSE does not
actually store any data itself. It is actually a built-in client which
allows MySQL server to talk to searchd, run search queries, and obtain
search results. All indexing and searching happen outside MySQL.

See http://sphinxsearch.com/docs/current.html#sphinxse-overview
   2014-10-09 15:45:06 by Thomas Klausner | Files touched by this commit (456)
Log message:
Remove SVR4_PKGNAME, per discussion on tech-pkg.
   2014-10-01 10:34:23 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
Changes 5.6.21:
The --skip-innodb option is now deprecated and its use results in a warning. It \ 
will be removed in a future MySQL release. This also applies to its synonyms \ 
(--innodb=OFF, --disable-innodb, and so forth).

MySQL Enterprise Edition now includes a set of encryption functions based on the \ 
OpenSSL library that expose OpenSSL capabilities at the SQL level.

Replication: The new variable simplified_binlog_gtid_recovery can be used to \ 
change the way binary log files are searched for previous GTIDs during recovery, \ 
speeding up the process when a large number of binary log files exist.

Internally, spatial data types such as Geometry are represented as BLOB values, \ 
so when invoked with the --hex-blob option, mysqldump now displays spatial \ 
values in hex.

Bugs Fixed...

Next | Query returned 74 messages, browsing 41 to 50 | Previous