Mysql 56 log_bin_basename
The default delay is 0 seconds. Delayed replication can be used for purposes such as protecting against user mistakes on the master a DBA can roll back a delayed slave to the time just before the disaster or testing how the system behaves when there is a lag.
This variable contains the complete filename and path to the binary log file. MySQL Replication now supports parallel execution of transactions with multi-threading on the slave. The current implementation of multi-threading on the slave assumes that data and updates are partitioned on a per-database basis, and that updates within a given database occur in the same relative order as they do on the master. However, it is not necessary to coordinate transactions between different databases.
Transactions can then also be distributed per database, which means that a worker thread on the slave slave can process successive transactions on a given database without waiting for updates to other databases to complete. Since transactions on different databases can occur in a different order on the slave than on the master, simply checking for the most recently executed transaction is not a guarantee that all previous transactions on the master have been executed on the slave.
This has implications for logging and recovery when using a multi-threaded slave. These query optimizer improvements were implemented:. The optimizer now more efficiently handles queries and subqueries of the following form:. That type of query is common in web applications that display only a few rows from a larger result set.
Reading rows using a range scan on a secondary index can result in many random disk accesses to the base table when the table is large and not stored in the storage engine's cache. Then the keys are sorted and finally the rows are retrieved from the base table using the order of the primary key.
The motivation for Disk-sweep MRR is to reduce the number of random disk accesses and instead achieve a more sequential scan of the base table data. The storage engine then evaluates the pushed index condition by using the index entry and only if this is satisfied is base row be read. ICP can reduce the number of accesses the storage engine has to do against the base table and the number of accesses the MySQL server has to do against the storage engine.
The optimizer more efficiently handles subqueries in the FROM clause that is, derived tables. Materialization of subqueries in the FROM clause is postponed until their contents are needed during query execution, which improves performance.
In addition, during query execution, the optimizer may add an index to a derived table to speed up row retrieval from it. The optimizer uses semi-join and materialization strategies to optimize subquery execution.
A Batched Key Access BKA join algorithm is now available that uses both index access to the joined table and a join buffer. The BKA algorithm supports inner join, outer join, and semi-join operations, including nested outer joins and nested semi-joins. Benefits of BKA include improved join performance due to more efficient table scanning. The optimizer now has a tracing capability, primarily for use by developers.
In addition, several deficiencies in condition handler processing rules were corrected so that MySQL behavior is more like standard SQL:.
Block scope is used in determining which handler to select. Previously, a stored program was treated as having a single scope for handler selection. Diagnostics area clearing has changed. Bug caused handled conditions to be cleared from the diagnostics area before activating the handler. This made condition information unavailable within the handler.
The condition information is cleared when the handler exits, if it has not already been cleared during handler execution. Previously, handlers were activated as soon as a condition occurred. Now they are not activated until the statement in which the condition occurred finishes execution, at which point the most appropriate handler is chosen.
This can make a difference for statements that raise multiple conditions, if a condition raised later during statement execution has higher precedence than an earlier condition and there are handlers in the same scope for both conditions.
Previously, the handler for the first condition raised would be chosen, even if it had a lower precedence than other handlers. Now the handler for the condition with highest precedence is chosen, even if it is not the first condition raised by the statement.
This restriction has been lifted. MySQL now provides more information about the causes of errors that occur when clients connect to the server, as well as improved access to the host cache, which contains client IP address and host name information and is used to avoid DNS lookups.
These changes have been implemented:. The OpenGIS specification defines functions that test the relationship between two geometry values. MySQL originally implemented these functions such that they used object bounding rectangles and returned the same result as the corresponding MBR-based functions.
Corresponding versions are now available that use precise object shapes. The following features are deprecated in MySQL 5. Where alternatives are shown, applications should be updated to use them. For applications that use features deprecated in MySQL 5. To avoid such problems, applications that use features deprecated in 5.
The motivation for the change in MySQL 5. To make advance preparation for an upgrade to MySQL 5. For reference, the full 5.
Enable plugin by running the following from the command line client: After that, make sure you can connect to ldap and that you can search ldap with ldapsearch, which you can verify with: I hope this helps.
There were no major functionality changes, but there was one security fix, 6 crashing bugs fixed, some general upstream fixes, and quite a few bug fixes, so let me cover the highlights: Server crash on updates with joins still on XtraDB upgraded to 5. If interested, the official MariaDB 5. Encryption for temporary files: Spider updated to 3. Thanks to Mark Callaghan for the contribution. To display passwords in cleartext, use the new —show option.
In addition to those, there were 55 other bug fixes: When using semisynchronous replication performance was degrading when the number of threads increased beyond a certain threshold. To improve performance, now only the thread which is committing is responsible for deleting the active transaction node. All other operations do not touch this active transaction list. 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. This could cause a deadlock. The memory used in the process of updating the table was not being freed correctly and this could lead to an out of memory error. The fix ensures that after an event is flushed to the relay log file by a receiver thread, the memory used is freed.
Bug , Bug Replication: Using mysqlbinlog to process log events greater than 1. This was caused by an internal error converting the length variable. The fix upgrades the length variable to avoid overflow in both encoding and decoding functions. Bug Incorrect Results: For join queries with a large number of tables, the server could exit converting the join to a semi-join. And if you do not want to test this for the Linux user account, then you may skip steps 2 and 3.
This should allow you to login. Now you can move on to integrating LDAP. Verify the LDAP user exists with: Here is a sample configuration: Note I obtained the sample ldap.
If you want to know more about user mapping, you should read this post by Geoff Montee as well as this post by Alexander Rubin. There were no major functionality changes, but there was one security fix, 6 crashing bugs fixed, some general upstream fixes, and quite a few bug fixes, so let me cover the highlights:. Given the security fix, you may want to consider upgrading if that particular CVE is of concern to you.
Also, please review the crashing bugs to see if they might affect you, and upgrade if so. This is a maintenance release, and no major changes, so there are only several noteworthy items but one of those being a security fix and five potential crashing bug:.
Given the security fix, you may want to review the CVE to see if this is something you need to address. This is the 3rd beta, and 6th overall, release of MariaDB There were not many major changes in this release, but a few notable items, as well as many overall bugs fixed I counted The highlights for me are 5 of the replication bugs, 1 partitioning bug, 1 performance-related bug, 1 wrong results bug, and 9 crashing bugs:.
Out of the 15 bugs, there were 5 InnoDB bugs 1 of which also spans partitioning , 1 security-related bug, 1 performance-related, and 3 additional potential crashing bugs. This is the 2nd beta, and 5th overall, release of MariaDB Now that it is beta, there were not as many major changes in this release compared to Of course it goes without saying that do not use this for production systems as it is only the 2nd beta release of To me, these are the highlights: Connect updated to 1.
Mroonga updated to 5. You can read more about the When using a multi-threaded slave, each worker thread has its own queue of transactions to process.
Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. In addition, two new status variables are available.