Percona is glad to announce the release ofPercona XtraDB Cluster5.5.37-25.10 on May 8, 2014. Binaries are available from thedownloads areaor from oursoftware repositories.
Based onPercona Server 5.5.37-35.0including all the bug fixes in it, Galera Replicator 2.10 (including fixes in2.9and2.10milestones) and on wsrep API 25.10 (including fixes in 25.10),Percona XtraDB Cluster5.5.37-25.10is now the current stable release. All of Percona‘s software is open-source and free.
New Features:
- Percona XtraDB Clusternow supports stream compression/decompression with new xtrabackup-sstcompressor/decompressoroptions.
-
Garbd
init script and configuration files have been packaged forCentOSandDebian, in addition, inDebiangarbd
is packaged separately inpercona-xtradb-cluster-garbd-2.x
package. - New meta packages are now available in order to make thePercona XtraDB Clusterinstallationeasier.
- Debian/Ubuntudebug packages are now available for Galera and garbd.
- New SST options have been implemented:inno-backup-opts, inno-apply-opts, inno-move-optswhich pass options to backup, apply and move stages of
innobackupex
. - Initial configurable timeout, of 100 seconds, to receive a first packet via SST has been implemented, so that if donor dies somewhere in between, joiner doesn’t hang. Timeout can be configured with thesst-initial-timeoutvariable.
- The joiner would wait and not fall back to choosing other potential donor nodes (not listed inwsrep_sst_donor) by their state. This happened even when comma was added at the end. This fixes it for that particular case.
- Support for Query Cache has been implemented.
- Percona XtraDB Cluster packages are now available for Ubuntu 14.04.
Bugs Fixed:
- To avoid disabling Parallel Apply in case of
SAVEPOINT
orROLLBACK TO SAVEPOINT
thewsrep_cert_deps_distancewas set to1.0
at all times. Bug fixed#1277703. - First connection would hang after changing thewsrep_cluster_addressvariable. Bug fixed#1022250.
- When
gmcast.listen_addr
variable was set manually it did not allow node’s own address ingcomm
address list. Bug fixed#1099478. -
wsrep_sst_rsync
would silently fail on joiner whenrsync
server port was already taken. Bug fixed#1099783. - Server would segfault on
INSERT DELAYED
withwsrep_replicate_myisamset todue to unchecked dereference ofNULL
pointer. Bug fixed#1165958. - When
grastate.dat
file was not getting zeroed appropriately it would lead to RBR error during the IST. Bug fixed#1180791. - Due to the
Provides:
line inPercona XtraDB Cluster(which providesPercona-Server-server
), the commandyum install Percona-Server-server
would installPercona XtraDB Clusterinstead of the expectedPercona Server. Bug fixed#1201499. - Replication of partition tables without binlogging enabled failed, partition truncation didn’t work because of lack of TO isolation there. Bug fixed#1219605.
- Exception during group merge after partitioning event has been fixed. Bug fixed#1232747.
- Default value for
binlog_format
is nowROW
. This is done so thatPercona XtraDB Clusteris not started with wrong defaults leading to non-deterministic outcomes like crash. Bug fixed#1243228. -
CREATE TABLE AS SELECT
was not replicated, if the select result set was empty. Bug fixed#1246921. -
INSERT
would return deadlock instead of duplicate key on secondary unique key collision. Bug fixed#1255147. - Joiner node would not initialize storage engines if
rsync
was used for SST and the first view was non-primary. Bug fixed#1257341. - Table level lock conflict resolving was releasing the wrong lock. Bug fixed#1257678.
- Resolved the perl dependencies needed forPercona XtraDB Cluster5.5. Bug fixed#1258563.
- Obsolete dependencies have been removed fromPercona XtraDB Cluster. Bug fixed#1259256.
- GCache file allocation could fail if file size was a multiple of page size. Bug fixed#1259952.
- Percona XtraDB Clusterdidn’t validate the parameters ofwsrep_provider_optionswhen starting it up. Bug fixed#1260193.
- Runtime checks have been added for dynamic variables which are Galera incompatible. Bug fixed#1262188.
- Node would get stuck and required restart if DDL was performed after
FLUSH TABLES WITH READ LOCK
. Bug fixed#1265656. - xtrabackup-v2is now used as default SST method inwsrep_sst_method. Bug fixed#1268837.
-
FLUSH TABLES WITH READ LOCK
behavior on the same connection was changed to conform toMySQLbehavior. Bug fixed#1269085. - Read-only detection has been added in
clustercheck
, which can be helpful during major upgrades (this is used byxinetd
forHAProxyetc.) Bug fixed#1269469. - Binary log directory is now being cleanup as part of the XtraBackup SST. Bug fixed#1273368.
- Deadlock would happen when
NULL
unique key was inserted. Workaround has been implemented to supportNULL
keys, by using themd5
sum of full row as key value. Bug fixed#1276424.
This release contains almost 100 fixed bugs, complete list of fixed bugs can be found in ourrelease notes.
Please see the5.5.37-25.10 releases notesfor complete details on all of the new features and bug fixes. Help us improve quality by reporting any bugs you encounter using ourbug tracking system. As always, thanks for your continued support of Percona!
Percona XtraDB ClusterErratacan be found in our documentation.

InnoDBBufferPool reduces disk I/O by caching data and indexing pages, improving database performance. Its working principle includes: 1. Data reading: Read data from BufferPool; 2. Data writing: After modifying the data, write to BufferPool and refresh it to disk regularly; 3. Cache management: Use the LRU algorithm to manage cache pages; 4. Reading mechanism: Load adjacent data pages in advance. By sizing the BufferPool and using multiple instances, database performance can be optimized.

Compared with other programming languages, MySQL is mainly used to store and manage data, while other languages such as Python, Java, and C are used for logical processing and application development. MySQL is known for its high performance, scalability and cross-platform support, suitable for data management needs, while other languages have advantages in their respective fields such as data analytics, enterprise applications, and system programming.

MySQL is worth learning because it is a powerful open source database management system suitable for data storage, management and analysis. 1) MySQL is a relational database that uses SQL to operate data and is suitable for structured data management. 2) The SQL language is the key to interacting with MySQL and supports CRUD operations. 3) The working principle of MySQL includes client/server architecture, storage engine and query optimizer. 4) Basic usage includes creating databases and tables, and advanced usage involves joining tables using JOIN. 5) Common errors include syntax errors and permission issues, and debugging skills include checking syntax and using EXPLAIN commands. 6) Performance optimization involves the use of indexes, optimization of SQL statements and regular maintenance of databases.

MySQL is suitable for beginners to learn database skills. 1. Install MySQL server and client tools. 2. Understand basic SQL queries, such as SELECT. 3. Master data operations: create tables, insert, update, and delete data. 4. Learn advanced skills: subquery and window functions. 5. Debugging and optimization: Check syntax, use indexes, avoid SELECT*, and use LIMIT.

MySQL efficiently manages structured data through table structure and SQL query, and implements inter-table relationships through foreign keys. 1. Define the data format and type when creating a table. 2. Use foreign keys to establish relationships between tables. 3. Improve performance through indexing and query optimization. 4. Regularly backup and monitor databases to ensure data security and performance optimization.

MySQL is an open source relational database management system that is widely used in Web development. Its key features include: 1. Supports multiple storage engines, such as InnoDB and MyISAM, suitable for different scenarios; 2. Provides master-slave replication functions to facilitate load balancing and data backup; 3. Improve query efficiency through query optimization and index use.

SQL is used to interact with MySQL database to realize data addition, deletion, modification, inspection and database design. 1) SQL performs data operations through SELECT, INSERT, UPDATE, DELETE statements; 2) Use CREATE, ALTER, DROP statements for database design and management; 3) Complex queries and data analysis are implemented through SQL to improve business decision-making efficiency.

The basic operations of MySQL include creating databases, tables, and using SQL to perform CRUD operations on data. 1. Create a database: CREATEDATABASEmy_first_db; 2. Create a table: CREATETABLEbooks(idINTAUTO_INCREMENTPRIMARYKEY, titleVARCHAR(100)NOTNULL, authorVARCHAR(100)NOTNULL, published_yearINT); 3. Insert data: INSERTINTObooks(title, author, published_year)VA


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

Dreamweaver Mac version
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool

WebStorm Mac version
Useful JavaScript development tools