With MySQL Enterprise Backup(MEB) 3.9.0 we had introduced
full instance backup feature for cloning the
MySQL server. Now with MEB 3.11.0 we have enhanced the feature by
copying all the master-slave setup files like MySQL server binary
logs(will be referred as 'binlogs'), binary log index files,
relay logs of slave, relay log index files, master info of slave,
slave info files. As part of full instance backup, copying of
binlog files is default behavior MEB-3.11.0 onwards. DBA should
be aware of the fact that current full instance backup is bigger
than the backups with old MEB's.
As every event on MySQL production database goes as a entry to
binlog files in particular format, binlog files could be huge.
Backing of huge binlog and/or relaylog files should not impact
the performance of MySQL server. Hence, all the binlog files, …
Having reviewed different table structures designed by different people, I have come to the conclusion that binary and non-binary string data types are used without consideration of the consequences of choosing either one. The confusion stems from the fact that both non-binary and binary string data appear to store characters because they can be saved as quoted string.
I don't feel like it to change my patches with every new release of PHP. In order to give something back to the community and to support my laziness, I publish a few patches for the PHP language. Some are really useful, some are quite okay and others are only to help in a more particular case. But read over the new featureset to make you an own opinion.
|
Users familiar with the MySQL development process will remember that our developers use a tool called pushbuild, which builds the server code with the latest changes, using several operating systems, and runs the test suite. |
This tool produces one binary package for each platform where the test runs, and every day there are a few dozen of such packages, waiting to be deleted and replaced by the ones created with the next build.
For long time, several people suggested publishing these binaries for the community. Each time, there was some minor or major impediment, such as getting together different teams and requesting resources from a third one. But the community …
[Read more]|
Users familiar with the MySQL development process will remember that our developers use a tool called pushbuild, which builds the server code with the latest changes, using several operating systems, and runs the test suite. |
This tool produces one binary package for each platform where the test runs, and every day there are a few dozen of such packages, waiting to be deleted and replaced by the ones created with the next build.
For long time, several people suggested publishing these binaries for the community. Each time, there was some minor or major impediment, such as getting together different teams and requesting resources from a third one. But the community …
[Read more]|
Users familiar with the MySQL development process will remember that our developers use a tool called pushbuild, which builds the server code with the latest changes, using several operating systems, and runs the test suite. |
This tool produces one binary package for each platform where the test runs, and every day there are a few dozen of such packages, waiting to be deleted and replaced by the ones created with the next build.
For long time, several people suggested publishing these binaries for the community. Each time, there was some minor or major impediment, such as getting together different teams and requesting resources from a third one. But the community …
[Read more]“There are 10 types of people in the world — those who understand binary, and those who don’t.”
The term “binary” in MySQL has many different meanings. How many can you come up with? I have 6, but I am willing to believe there are more!
0) “Binary distribution” is the name for the package that
contains a binary. Another use is “binary installation” but
that’s pretty much the same usage pattern as “binary
distribution”, so I won’t count “binary installation” as a
separate usage.
1) “Server binary” or “client binary” is the actual program
(mysqld, mysql).
2) “Binary format” is a compressed format. For example,
DECIMAL is stored in a “binary format” — each group
of nine digits is compressed into 4 bytes.
3) “Binary log” is the change log. You can argue that this is an
extension of #3, because the binary log is a compressed …
Recently I had an interesting issue crop up. Due to an
unfortunate migration incident in which involved master/master
replication and not checking to see if replication was caught up,
we ended up with an infinite replication loop of a number of SQL
statements. awk helped immensely in the aftermath
cleanup.
The basics of the replication infinite loop were (more…)
|
After a long delay, a new community binary has been released. MySQL 5.0.67 has reached the mirrors and it's ready for download. The list of changes is quite long and includes a tiny incompatible change. Every version of MySQL ships with sample option files, called my-small.cnf, my-large.cnf, my-huge.cnf.cnf. In this version, these files contain a line saying |
The MySQL Community version is different in theory from the Enterprise version in relation to the following points:
0) It’s free
1) It has community patches
2) It is released less often
3) It is tested less strictly
In reality, the first two differences are not applicable — the binaries and source code for Enterprise can be freely and legally downloaded at http://mirror.provenscaling.com/mysql/enterprise/. The process for adding community patches to the MySQL source code has not been changed sufficiently to be able to actually add community patches and encourage more community development.
I understand that MySQL (and now Sun) needs to make money. I also understand that development takes a lot of effort, and seeing an ROI is important. The Community/Enterprise split was designed to have tradeoffs on both sides. …
[Read more]