Problems found with existing distfiles:
distfiles/D6.data.ros.gz
distfiles/cstore0.2.tar.gz
distfiles/data4.tar.gz
distfiles/sphinx-2.2.7-release.tar.gz
No changes made to the cstore or mariadb55-client distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Update home page & master site, clean up.
PgBouncer 1.6.1.
- Security fix for CVE-2015-6817.
- Per-pool pooling mode vs. reset query.
Details:
http://pgbouncer.github.io/2015/09/pgbouncer-1-6-1/
PgBouncer 1.6.0
Main new features:
- Load user password hash from postgres database.
- Pooling mode can be configured both per-database and per-user.
- Per-database and per-user connection limits: max_db_connections and
max_user_connections.
- Add DISABLE/ENABLE commands to prevent new connections.
- New preferred DNS backend: c-ares.
- Config files have %include FILENAME directive to allow configuration
to be split into several files.
Details:
http://pgbouncer.github.io/2015/08/pgbouncer-1-6/
PgBouncer 1.5.5
- Fix remote crash - invalid packet order causes lookup of NULL pointer.
Not exploitable, just DoS.
The Apache Cassandra Project develops a highly scalable second-generation
distributed database, bringing together Dynamo's fully distributed design
and Bigtable's ColumnFamily-based data model.
on the 1.x branch. Set up Makefile.common to be used by newer versions.
1.2.19
* Don't index tombstones
* Don't allow compacted sstables to be marked as compacting
* Track expired tombstones
* Validate empty cell names from counter updates
* Improve PasswordAuthenticator default super user setup
* Remove duplicates from StorageService.getJoiningNodes
* Clone token map outside of hot gossip loops
* Add stop method to EmbeddedCassandraService
* Support connecting to ipv6 jmx with nodetool
* Set gc_grace_seconds to seven days for system schema tables
* SimpleSeedProvider no longer caches seeds forever
* Set correct stream ID on responses when non-Exception Throwables
are thrown while handling native protocol messages
* Fix row size miscalculation in LazilyCompactedRow
* Fix race in background compaction check
* Don't clear out range tombstones during compaction
1.2.18
* Support Thrift tables clustering columns on CqlPagingInputFormat
* Fix compilation with java 6 broke by CASSANDRA-7147
1.2.17
* cqlsh: Fix CompositeType columns in DESCRIBE TABLE output
* Expose global ColumnFamily metrics
* Handle possible integer overflow in FastByteArrayOutputStream
* cqlsh: 'ascii' values weren't formatted as text
* cqlsh: ignore .cassandra permission errors
* reduce failure detector initial value to 2s
* Fix problem truncating on a node that was previously in a dead state
* Don't insert tombstones that hide indexed values into 2i
* Track metrics at a keyspace level
* Add replace_address_first_boot flag to only replace if not bootstrapped
* Enable keepalive for native protocol
* Check internal addresses for seeds
* Fix potential / by 0 in HHOM page size calculation
* Fix handling of empty counter replication mutations
* Use LOCAL_ONE for non-superuser auth queries
* Set keepalive on MessagingService connections
* Add Cloudstack snitch
* Update system.peers correctly when relocating tokens
* Add Google Compute Engine snitch
* Fix nodetool display with vnodes
* Fix schema concurrency exceptions
* Fix BatchlogManager#deleteBatch() use of millisecond timsestamps
* Continue assassinating even if the endpoint vanishes
* Schedule schema pulls on change
* Non-droppable verbs shouldn't be dropped from OTC
* Shutdown batchlog executor in SS#drain()
* Fix batchlog to account for CF truncation records
* Fix CQLSH parsing of functions and BLOB literals
* Require nodetool rebuild_index to specify index names
* Ensure that batchlog and hint timeouts do not produce hints
* Don't shut MessagingService down when replacing a node
* Always clean up references in SerializingCache
* fix npe when doing -Dcassandra.fd_initial_value_ms
* Preserves CQL metadata when updating table from thrift
* fix time conversion to milliseconds in SimpleCondition.await
* remove duplicate query for local tokens
* raise streaming phi convict threshold level
* reduce garbage creation in calculatePendingRanges
* exit CQLSH with error status code if script fails
* Fix bug with some IN queries missig results
* Fix availability validation for LOCAL_ONE CL
* Hint streaming can cause decommission to fail
* RepairTask didn't send a correct message on IllegalArgumentException
* Fix race in Thrift server that can exhaust the pool of worker threads
- Add support for the get-wal command which allows users to fetch any
WAL file from the archive of a specific server
- Add support for retry hook scripts, a special kind of hook scripts
that Barman tries to run until they succeed
- Add active configuration option for a server to temporarily disable
the server by setting it to False
- Add barman_lock_directory global option to change the location of
lock files (by default: 'barman_home')
- Execute the full suite of checks before starting a backup, and skip
it in case one or more checks fail
- Forbid to delete a running backup
- Analyse include directives of a PostgreSQL server during backup and
recover operations
- Add check for conflicting paths in the configuration of Barman, both
intra (by temporarily disabling a server) and inter-server (by
refusing any command, to any server).
- Add check for wal_level
- Add barman-wal-restore script to be used as restore_command on a
standby server, in conjunction with barman get-wal
- Implement a standard and consistent policy for error management
- Improved cache management of backups
- Improved management of configuration in unit tests
- Tutorial and man page sources have been converted to Markdown format
- Add code documentation through Sphinx
- Complete refactor of the code responsible for managing the backup
and the recover commands
- Changed internal directory structure of a backup
- Introduce copy_method option (currently fixed to rsync)
- Bug fixes:
- Manage options without '=' in PostgreSQL configuration files
- Preserve Timeline history files (Fixes: #70)
- Workaround for rsync on SUSE Linux (Closes: #13 and #26)
- Disables dangerous settings in postgresql.auto.conf
(Closes: #68)
- Fixed error in WAL rate calculation
mongo-c-driver 1.2.0
- Much improved reporting of network errors, unavailable servers, and
authentication failure
- Destroying an exhaust cursor must close its socket
- Various bugs in server reconnection logic
- mongoc_collection_aggregate returned invalid cursor after failure
- Wrong error message after failed network write on Sparc
- Missing JSON test files in release tarball
- Enable runtime asserts in release build.
- mongoc_client_kill_cursor is now deprecated and will be removed
in version 2.0.
mongo-c-driver 1.1.11
- Undetected network errors when sending messages to the server
- Off-by-one error in mongoc_gridfs_file_seek with mode SEEK_END
- Memory leak parsing a URI that contains an invalid option
2.0.0 (2015-10-14)
- Elasticsearch 2.0 compatibility release
1.8.0 (2015-10-14)
- removed thrift and memcached connections, if you wish to continue
using those, extract the classes and use them separately.
- added a new, parallel version of the bulk helper using thread pools
Fix the plugin script.
elasticsearch 1.7.3
===================
Enhancements
Tribe Node:
TransportNodesAction shouldn't hold on to cluster state
Bug fixes
Internal:
- An inactive shard is activated by triggered synced flush
- Pending operations in the translog prevent shard from being
marked as inactive
Mapping:
- Ensure more specific analyzer is used independent of the mapping order
REST:
- Expose nodes operation timeout in REST API
Snapshot/Restore:
- Snapshot restore operations throttle more than specified
Tribe Node:
- Increment tribe node version on updates
Upgrades
Network:
- Upgrade Netty to 3.10.5.final
elasticsearch 1.7.2
===================
Enhancements
Allocation:
- Avoid extra reroutes of delayed shards in RoutingService
Packaging:
- Shade joda-convert
Query DSL:
- Add a check if FieldMappers exists
Bug fixes
Allocation:
- Take relocating shard into consideration during awareness allocation
- Take initializing shards into consideration during awareness allocation
- Fix messaging about delayed allocation
Internal:
- Fix concurrency issue in PrioritizedEsThreadPoolExecutor.
Nested Docs:
- Nested query should only use bitset cache for parent filter
Packaging:
- Fix upgrade RPM script
Plugins:
- Plugin script: Fix ES_HOME with spaces
Query DSL:
- Do not track named queries that are null
- multi_match query applies boosts too many times.
Recovery:
- Rethrow exception during recovery finalization even if source is
not broken
Snapshot/Restore:
- Snapshot restore request should accept indices options
Suggesters:
- Prevent DirectCandidateGenerator to reuse an unclosed analyzer
--[ Redis 3.0.5 ] Release date: 15 Oct 2015
Upgrade urgency: MODERATE, the most important thing is a fix in the replication
code that may make the slave hanging forever if the master
remains with an open socket even if it is no longer able to
reply.
* [FIX] MOVE now moves the TTL as well. A bug lasting forever... finally
fixed thanks to Andy Grunwald that reported it.
(reported by Andy Grunwald, fixed by Salvatore Sanfilippo)
* [FIX] Fix a false positive in HSTRLEN test.
* [FIX] Fix a bug in redis-cli --pipe mode that was not able to read back
replies from the server incrementally. Now a mass import will use
a lot less memory, and you can use --pipe to do incremental streaming.
(reported by Twitter user @fsaintjacques, fixed by Salvatore
Sanfilippo)
* [FIX] Slave detection of master timeout. (fixed by Kevin McGehee, refactoring
and regression test by Salvatore Sanfilippo)
* [NEW] Cluster: redis-trib fix can fix an additional case for opens lots.
(Salvatore Sanfilippo)
* [NEW] Cluster: redis-trib import support for --copy and --replace options
(David Thomson)
--[ Redis 3.0.4 ] Release date: 8 Sep 2015
Upgrade urgency: HIGH for Redis and Sentinel. However note that in order to
fix certain replication bugs, the replication internals were
modified in a very heavy way. So while this release is
conceptually saner, it may contain regressions. For this
reason, before the release, QA activities were performed by
me (antirez) and Redis Labs and no evident bug was found.
* [FIX] A number of bugs related to replication PSYNC and the (yet experimental)
diskless replication feature were fixed. The bugs could lead to
inconsistency between masters and slaves. (Salvatore Sanfilippo, Oran
Agra fixed the issue found by Yuval Inbar)
* [FIX] A replication bug in the context of PSYNC partial resynchonization was
found and fixed. This bug happens even when diskless replication is off
in the case different slaves connect at different times while the master
is creating an RDB file, and later a partial resynchronization is
attempted by a slave that connected not as the first one. (Salvatore
Sanfilippo, Oran Agra)
* [FIX] Chained replication and PSYNC interactions leading to potential stale
chained slaves data set, see issue #2694. (Salvatore Sanfilippo fixed
an issue reported by "GeorgeBJ" user at Github)
* [FIX] redis-cli --scan iteration fixed when returned cursor overflows
32 bit signed integer. (Ofir Luzon, Yuval Inbar)
* [FIX] Sentinel: fixed a bug during the master switch process, where for a
failed conditional check, the new configuration is rewritten, during
a small window of time, in a corrupted way where the master is
also reported to be one of the slaves. This bug is rare to trigger
but apparently it happens in the wild, and the effect is to see
a replication loop where the master will try to replicate with itself.
The bug was found by Jan-Erik Rediger using a static analyzer and
fixed by Salvatore Sanfilippo.
* [FIX] Sentinel lack of arity checks for certain commands.
(Rogerio Goncalves, Salvatore Sanfilippo)
* [NEW] Replication internals rewritten in order to be more resistant to bugs.
The replication handshake in the slave side was rewritten as a non
blocking state machine. (Salvatore Sanfilippo, Oran Agra)
* [NEW] New "replication capabilities" feature introduced in order to signal
from the master to the slave what are the features supported, so that
the master can choose the kind of replication to start (diskless or
not) when master and slave are of different versions. (Oran Agra,
Salvatore Sanfilippo)
* [NEW] Log clients details when SLAVEOF command is received. (Salvatore
Sanfilippo with inputs from Nick Craver and Marc Gravell).
Changelog:
3.0.7 – Oct 13, 2015
Improvements to WiredTiger memory handling and performance: SERVER-20159, SERVER-20204, SERVER-20091, and SERVER-20176.
Fixed issue where replica set nodes will not step down: SERVER-19464.
Additional privileges for built-in roles: SERVER-19131, SERVER-15893, and SERVER-13647.
All issues closed in 3.0.7
Fix the json1 extension so that it does not recognize ASCII form-feed as a whitespace character, in order to comply with RFC-7159.
Add a few #ifdef and build script changes to address compilation issues that appeared after the 3.9.0 release.
Policy Changes:
* The version numbering conventions for SQLite are revised to use the emerging standard of semantic versioning.
New Features And Enhancements:
* Added the json1 extension module in the source tree, and in the amalgamation. Enable support using the SQLITE_ENABLE_JSON1 compile-time option.
* Added Full Text Search version 5 (FTS5) to the amalgamation, enabled using SQLITE_ENABLE_FTS5. FTS5 will be considered "experimental" (subject to incompatible changes) for at least one more release cycle.
* The CREATE VIEW statement now accepts an optional list of column names following the view name.
* Added support for indexes on expressions.
* Added support for table-valued functions in the FROM clause of a SELECT statement.
* Added support for eponymous virtual tables.
* A VIEW may now reference undefined tables and functions when initially created. Missing tables and functions are reported when the VIEW is used in a query.
* Added the sqlite3_value_subtype() and sqlite3_result_subtype() interfaced (used by the json1 extension).
* The query planner is now able to use partial indexes that contain AND-connected terms in the WHERE clause.
* The sqlite3_analyzer.exe utility is updated to report the depth of each btree and to show the average fanout for indexes and WITHOUT ROWID tables.
* Enhanced the dbstat virtual table so that it can be used as a table-valued function where the argument is the schema to be analyzed.
Other changes:
* The sqlite3_memory_alarm() interface, which has been deprecated and undocumented for 8 years, is changed into a no-op.
Important fixes:
* Fixed a critical bug in the SQLite Encryption Extension that could cause the database to become unreadable and unrecoverable if a VACUUM command changed the size of the encryption nonce.
* Added a memory barrier in the implementation of sqlite3_initialize() to help ensure that it is thread-safe.
* Fix the OR optimization so that it always ignores subplans that do not use an index.
* Do not apply the WHERE-clause pushdown optimization on terms that originate in the ON or USING clause of a LEFT JOIN.
=== 1.3.11 / 2015-10-10
* Enhancements:
* Windows: build against SQLite 3.8.11.1
* Internal:
* Use rake-compiler-dock to build Windows binaries. Pull #159 [larskanis]
* Expand Ruby versions being tested for Travis and AppVeyor
MySQLTuner is a script written in Perl that will assist you with your MySQL
configuration and make recommendations for increased performance and
stability.
Two security issues have been fixed in this release which affect users of specific PostgreSQL features:
CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service.
CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
Two security issues have been fixed in this release which affect users of specific PostgreSQL features:
CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service.
CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
Two security issues have been fixed in this release which affect users of specific PostgreSQL features:
CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service.
CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
Two security issues have been fixed in this release which affect users of specific PostgreSQL features:
CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service.
CVE-2015-5288: The crypt() function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed.
Bugs fixed
- fixed a bug with the Cython speedups not being included
in package.
- documented how to create models with no primary key.
- allow bare INSERT statements.
- regarding foreign key / one-to-one relationships.
- allow ArrayField to accept tuples in addition to lists.
- fix regarding unsaved relations.
- refactored QueryResultWrapper to allow multiple independent
iterations over the same underlying result cache.
- fix bug with multiple joins to same table + eager loading.
- fix bug when connection fails while using an execution context.
- use correct column names with non-standard django foreign keys.
- return datetime.time instead of timedelta for MySQL time fields.
- fixed SQLite migrator regular expressions. Thanks @sroebert.
New features
- added support for RETURNING clauses. Update, Insert and Delete
queries can now be called with RETURNING to retrieve the rows
that were affected.
- added web request hook docs.
- allowed arbitrary model attributes and methods to be serialized
by model_to_dict(). Docs.
- allow model_to_dict() to introspect query for which fields
to serialize.
- Added backend-agnostic truncate_date() implementation.
- Added a FixedCharField which uses column type CHAR.
- Added support for arbitrary PRAGMA statements to be run on new
SQLite connections. Docs.
- Removed berkeley_build.sh script. See instructions on my blog
instead.
Add missing DEPENDS
Upstream changes:
version 0.2102 at 2015-03-29 09:46:45 +0000
-------------------------------------------
Change: 96eacfc5c44a2ac4c5f6ae5c4e8202c1e9f7c059
Author: Naveed Massjouni <naveed@vt.edu>
Date : 2015-03-29 05:44:09 +0000
this plugin is now a thin wrapper around DBICx::Sugar
I created DBICx::Sugar to factor out the code duplication between
Dancer::Plugin::DBIC and Dancer2::Plugin::DBIC. Now this plugin is
just a thin wrapper around DBICx::Sugar.
-------------------------------------------
version 0.2101 at 2015-02-14 02:52:24 +0000
-------------------------------------------
Change: b4b29aa82925bc53370ae15aa66e897085c31db5
Author: Naveed Massjouni <naveed@vt.edu>
Date : 2015-02-13 21:52:24 +0000
updated SQL::Translator version requirement to fix cpantesters
failures
Change: 2ee1a4bfad6362fad5907dfe85fb8d866835cef6
Author: Naveed Massjouni <naveedm9@gmail.com>
Date : 2015-01-12 01:16:15 +0000
Merge pull request #17 from monsieurp/test-code-refactoring
Test code refactoring
Change: c2b09c695a711a336e753771926c01d4a53a4c31
Author: Patrice Clement <monsieurp@gentoo.org>
Date : 2015-01-11 19:48:35 +0000
get rid of eval {} and make use of Test::Requires instead
Change: 9270cfe02c06f1de469d6e19171c3e8d1ecb2f47
Author: Patrice Clement <monsieurp@gentoo.org>
Date : 2015-01-10 20:32:36 +0000
test code refactoring and import tyding
Just some syntax sugar for your DBIx::Class applications. This was originally
created to remove code duplication between Dancer::Plugin::DBIC and
Dancer2::Plugin::DBIC.
=== 4.27.0 (2015-10-01)
* Don't stub Sequel.synchronize on MRI (YorickPeterse) (#1083)
* Make bin/sequel warn if given arguments that it doesn't use (jeremyevans)
* Fix the order of referenced composite keys returned by Database#foreign_key_list on PostgreSQL (jeremyevans) (#1081)
* Recognize another disconnect error in the jdbc/postgresql adapter (jeremyevans)
* In the active model plugin, make Model#persisted? return false if the transaction used for creation is rolled back (jeremyevans) (#1076)
* Use primary_key :keep_order option in the schema dumper if the auto incrementing column is not the first column in the table (jeremyevans)
* Set :auto_increment option correctly in the schema parser when the auto incrementing column is not the first column in the table (jeremyevans)
* Support :keep_order option to primary_key in schema generator, to not automatically make the primary key the first column (jeremyevans)
* Add new jsonb/json functions and operators supported in PostgreSQL 9.5+ (jeremyevans)
* Add before_after_save plugin, for refreshing created objects and resetting modified flag before calling after_create/update/save hooks (jeremyevans)
* Add Dataset#single_record! and #single_value! which don't require cloning the receiver (jeremyevans)
* Dataset#with_sql_single_value now works correctly for model datasets (jeremyevans)
* Optimize Dataset#single_value and #with_sql_single_value to not create an unnecessary array (jeremyevans)
* Make postgres adapter work with postgres-pr 0.7.0 (jeremyevans) (#1074)
0.4.1
0.4.0
@sodabrew sodabrew released this 26 days ago · 54 commits to master since this
release
New Features
* Support for Prepared Statements!
* Add connection option :sslverify
* Use mariadb_config for MariaDB builds
Bugfixes
* Fix Mysql2::Result#count always returns 0 when using stored procedures and
MULTI_STATEMENTS
Changes
* Prevent Timeout::timeout from interrupting query execution
* Use Ruby's String#encode to remove unrecognized characters from error messages
* Convert specs to RSpec 3 expect sytnax
* Refactored the Travis CI test scripts
* Misc cleanups with Rubocop
* Stricter CFLAGS
0.3.20
@sodabrew sodabrew released this on 25 Aug · 205 commits to master since this
release
Bugfixes
* Check if O_CLOEXEC is defined before using it in open()
* Fix an infinite loop while searching for libmysqlclient when mysql_config is
not found
Changes
* Call RakeCompilerDock.sh twice, once for 32-bit and once for 64-bit, when
building Windows binary gems
0.3.19
@sodabrew sodabrew released this on 30 Jul · 205 commits to master since this
release
New Features
* Mysql2::Client#info class method for easier debugging, and both the class
and instance method return US_ASCII output rather than using the connection
encoding.
* When streaming results, continue result.count across calls to result.each
Bugfixes
* Search for mariadb_config on compile
* Update to Connector/C 6.1.6 in the Windows builds
* Fix Mysql2::Client#escape to set the encoding even if the string was not
modified
* Fix LICENSE filename in gem file list
* Make the result.count return type consistent and match the source type
Changes
* Rename macro GetMysql2Result to GET_RESULT
* Convert StringValuePtr to either RSTRING_PTR or StringValueCStr
* Fix unused variable warning on Windows in rb_mysql_client_socket
* Add Ruby 2.2 to the AppVeyor matrix
* Test default client flag equality instead of bitwise truthiness
* Add rake-compiler-dock for building Windows binary gems
* Friendly ext build error <3
* Process :stream option in rb_mysql_result_to_obj once instead of
rb_mysql_result_each for each call to each
* Tests for streaming and stored procedures with multiple result sets
* Connector/Python is now compatible with Django 1.8.
* When using the C Extension with raise_on_warnings=True, errors were not thrown as exceptions when an executed statement produced an error, and it was not possible to reuse the cursor if the statement produced a result set.
* When using the C Extension, character decoding of identifiers (database, table, column names) in result sets could fail.
* When using the C Extension with the auth_plugin option, connect() calls failed.
* In connections for which consume_results=True, callproc() could hang.
* Connections failed if the password began or ended with spaces because they were being stripped before the connection attempt.
* Connection failure occurred for accounts authenticated with the sha256_password authentication plugin that had a blank password.
* The Connector/Python C Extension could exit when fetching a result set containing many NULL values.
* Connector/Python failed to complete the connection handshake with MySQL Server 5.5.8.
* InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems.
* yaSSL was upgraded to version 2.3.8.
* RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed.
* InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset.
* InnoDB: Memory allocation sanity checks were added to the memcached code.
* InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code.
* InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word.
* InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20.
* InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation.
* InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available.
* InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system.
* InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied.
* InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format.
* Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected.
* Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly
* Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE.
* Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert.
* Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
* yaSSL was upgraded to version 2.3.8.
* InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word.
* InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. Thanks to Alexey Kopytov for the patch.
* InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available.
* InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system.
* Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected.
* Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE.
* Certain subqueries as arguments to PROCEDURE ANALYSE() could cause a server exit.
* mysql_ssl_rsa_setup could create an unwanted .rnd file in the data directory. (The file is actually created by openssl, which mysql_ssl_ras_setup invokes. mysql_ssl_rsa_setup now cleans up the file.)
* An assertion could be raised due to incorrect error handling if a SELECT ... FOR UPDATE subquery resulted in deadlock and caused a rollback.
* Servers linked against yaSSL and compiled with GCC 4.8.2 could fail to respond correctly to connection attempts until several seconds after startup.
* For tables with subpartitions, the server could exit due to incorrect error handling during partition pruning if the partition could be identified but not the subpartition.
* DELETE could check privileges for the wrong database when table aliases were used.
* Within a trigger, use of a cursor that accessed OLD or NEW values from a row could cause a server exit.
* MySQL sometimes produced no warning when it was unable to interpret a character in a given character set.
* For MySQL distributions linked against yaSSL, a corrupt client key file could cause clients to exit.
* Execution of certain BINLOG statements while temporary tables were open by HANDLER statements could cause a server exit.
shared-mime-info 1.5 (2015-09-15)
* Fix compilation with glib < 2.26
* Update DTD
Mime-type changes:
* Add more globs to console ROM files
* Use "folder" generic-icon for inode/directory
* Bump priority for ISO images glob matching to work
around confusion around Wii image files
* Add application/owl+xml
* Add text/turtle
* Use IANA registered image/vnd.zbrush.pcx for PCX
* Add text/rust for Rust source code
* Add application/ld+json as subclass of application/json
* Add text/csv-schema
* Add application/vnd.coffeescript
* Make application/vnd.apple.mpegurl a subclass of text/plain
* Make application/sdp a subclass of text/plain
* Add application/jrd+json as subclass of application/json
* Add MTM, MED, 699 and Ultratracker magic for application/x-mod
* Add Meson build definitions
* Match newer versions of XCF files
* Use IANA registered type for PKCS#12
* Add application/x-doom-wad
* Add Amiga disk image
* Rename "Dreamcast ROM" to "Dreamcast GD-ROM"
* Add application/x-wii-wad
* Add magic and tests to application/x-gameboy-rom
* Add application/x-saturn-rom
* Fix application/x-genesis-rom translation rules
* Split up multi-page DjVu into its own mime-type
