June 20, 2013

Comment: Is Synchronous Replication right for your app?

… is really focused on the more typical workloads of a SQL database — small transactions.

Comment: Death match! EBS versus SSD price, performance, and QoS

… be a problem. The AWS instance we use (for our SQL Server) does have two ephemeral SSDs. Since they are ephemeral…

Post: How to create a new (or repair a broken) GTID based slave with Percona XtraBackup

… status: slave1 > show slave status\G [...] Slave_IO_Running: Yes Slave_SQL_Running: Yes [...] Retrieved_Gtid_Set: c777888a-b6df-11e2-a604-080027635ef5…

Comment: Follow these basics when migrating to Percona XtraDB Cluster for MySQL

… updated which was never the case when we were on SQL. so i guess the problem is due to Percona. Please…

Comment: Follow these basics when migrating to Percona XtraDB Cluster for MySQL

… of Percona? as earlier it use to work fine on SQL. does it not support concurrent submission of a form (multiple…

Post: Percona XtraBackup 2.0.7 for MySQL available for download

… copying failure. Bug fixed #1170806. innobackupex would fail if the SQL_MODE was set to ANSI_QUOTES. Bug fixed #945161. Missing…

Comment: Be careful when joining on CONCAT

Hi there! Is there any ways to EXPLAIN the SQL which is imported from the SOURCE command! @@

Comment: CVE-2012-4414 strikes back in MySQL 5.5.29 (and what we're doing in Percona Server 5.5.29)

…, thank you for correcting me. I am able to cause sql injection due to truncation, I have opened a new bug…

Comment: CVE-2012-4414 strikes back in MySQL 5.5.29 (and what we're doing in Percona Server 5.5.29)

Incorrect truncation is certainly a vulnerability. Why would you say otherwise? For example, if a string litteral is truncated in the middle. Then a later string litteral will be parsed as SQL expression.

Post: Follow these basics when migrating to Percona XtraDB Cluster for MySQL

… replication inside PXC has an additional overhead, this means the SQL_THREAD will not be able to execute events as fast…