Just short message that patch enables microsecond resolution in slow-log (see more http://www…. 5.0.37 is available here: www.mysqlperformanceblog.com/files/patches/patch.slow-micro.5.0.37.diff The patch for 5.0.41 : www.mysqlperformanceblog.com/files/patches/patch.slow-micro.5.0.41…
Post: Global Transaction ID and other patches available!
… their internal mysql-team) made a great contribution to MySQL. Patches global transaction IDs, binlog event checksums and crash-safe replication… wall in using these patches that they were part of one big patch, which you can apply only to 5.0.37, and now there is no barrier to include patches into our builds…
Comment: Microslow patch for 5.0.37
The 5.0.41 patch seems to be a copy of the 5.0.37 patch!? I see no difference and it sais diff -ur mysql-5.0.37/include/my_time.h mysql-5.0.37-microslow/include/my_time.h
Comment: MySQL Users Conference - Innodb
… words. The patches from Google were first available for MySQL 4.0.26. They are now available for 4.0.26 and 5.0.37 — see http://code.google.com/p/google-mysql-tools to get them. There are two patches for 5.0.37, one that only has the changes for semi-sync replication and another that has everything. The changes for 4.0…
Post: MySQL Releases first real Community Release
Few days ago MySQL released MySQL 5.0.37 which I would call first real Community Version, because unlike … cool features to follow ? Jeremy’s PROFILE patches are great but I hope the patches will be continue to flow in. In… quality assurance to accepted code. What is about binaries ? MySQL 5.0.37 was rare exception of community release with binaries and if…
Post: Profiling MySQL stored routines
…_on_disk: No Merge_passes: 0 # No InnoDB statistics available for this query SELECT whatstheweatherlike(5); Not overly useful for query optimization… are being executed. This is where Jeremy’s SHOW PROFILE patch – which is included in all Community tree based Percona MySQL… since it is part of MySQL community version ever since 5.0.37 (note – not all Percona builds are done on Community tree…
Comment: Slow Query Log analyzes tools
[...] short message that patch enables microsecond resolution in slow-log (see more http://www.mysqlperformanceblog.com/2006/09/06/slow-query-log-analyzes-tools/) for 5.0.37 is available here: [...]
Post: What is stored InnoDB buffer pool
… is not so hard actually – we made a short patch for MySQL 5.0 which show innodb buffer pool content mysql> select * from… | 5 | unknown | | | | | 2 | 0 | 3 | 0 | 0 | 0 | 0 | 4 | 6 | unknown | | | | | 3 | 0 | 2 | 0 | 0 | 0 | 0 | 5 | 3 | inode | | | | | 4 | 0 | 4 | 0 | 0 | 0 | 0 | 6 | 17855 | index | CLUST_IND | | SYS_IBUF_TABLE_0 | | 5 | 0… | 17 | 1715 | 128 | 15077 | 0 | 0 | 70 | 17855 | index | GEN_CLUST_INDEX | art | a87 | | 69 | 17 | 37 | 1048 | 15720 | 0 | 0 | 71 | 17855 | index | GEN…
Post: Estimating Replication Capacity
…measure it: 1) Use “UserStats” functionality from Google patches, which is now available in Percona Server and…5.75k 124.25 # Bytes sen 1.94M 0 9.42k 1.67 0 110.38 0 # Killed 0 0 0 0 0 0 0 # Last errn 34.11M 0…load. This gives us replication capacity of 1/0.37 = 2.70 This method should work with …
Comment: Returning to InnoDB scalability
…you Vadim. I tried this patch. However, it became a hit to the bug and MySQL… 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46… [Note] /opt/mysql/bin/mysqld: ready for connections. Version: ‘5.0.22-log’ socket: ‘/tmp/mysql.sock’ port: 3306 Source distribution …

