Among the many things that can cause a “server stall” is a long-running transaction. If a transaction remains open for a very long time without committing, and has modified data, then other transactions could block and fail with a lock wait timeout. The problem is, it can be very difficult to find the […]Read more
Percona Server version 5.1.55-12.6 is now available for download. It is now the current stable release version.
Fixed compiler warnings in both the core server and in XtraDB. (Alxey Kopytov, Yasufumi Kinoshita)
Bug #602047 – The ROWS_READ columns of TABLE_STATISTICS and INDEX_STATISTICS were not properly updated when a query involved index lookups on an InnoDB […]Read more
We receive many requests for help with server stalls. They come under various names: lockup, freeze, sudden slowdown. When something happens only once or twice a day, it can be difficult to catch it in action. Unfortunately, this often leads to trial-and-error approaches, which can drag on for days (or even months), […]Read more
As Huey Lewis once noted, sometimes it’s “Hip To Be Square.” Apparently, occasionally, someone even pays attention to you when you are. Xconomy just featured “10 Boring Boston-Area Tech Companies That Are Actually Interesting” and we made the cut. As they note it is a “short list of the Boston area’s most boring-sounding tech […]Read more
A common misunderstanding about innodb_support_xa is that it enables user-initiated XA transactions, that is, transactions that are prepared and then committed on multiple systems, with an external transaction coordinator. This is actually not precisely what this option is for. It enables two-phase commit in InnoDB (prepare, then commit). This is necessary […]Read more