Yabomsat!
Yet Another Blog On MySQL® Server Administration, monitoring and Tuning!

Falcon vs InnoDB

May 31, 2008 - 12:14 pm - by Santo Leto

Yesterday, during the talk of Ivan Zoratti, at the meeting with Marten Mickos and the Italian Team of SUN | MySQL in Rome, there was a question about Falcon performance: a guy pointed out that InnoDB is better than Falcon.

Well, this is not really the truth.

How many processors are you using for Falcon benchmarking?

Falcon is designed to make optimal use of modern large-memory multi-CPU/multi-core hardware. So when comparing performance of Falcon and InnoDB, you can’t leave this out of consideration!

Please, see the shoots below:

falcon1.jpg falcon2.jpg
falcon3.jpg falcon4.jpg

To learn more on the Falcon engine, you can attend this webinar:

Also note please that Falcon is in a beta stage, not alpha. The 6.0 binary may be labeled ‘alpha’ but it does contain the Falcon transaction engine beta!

More Resources on the Falcon Engine:

  1. Falcon Feature Preview: http://forge.mysql.com/wiki/Falcon_Feature_Preview
  2. MySQL Forum dedicated to Falcon: http://forums.mysql.com/list.php?133
  3. MySQL 6.0 download: http://dev.mysql.com/downloads/mysql/6.0.html

Start playing with Falcon today! and thanks to the Falcon Team for their great and very interesting activities!


Re: Giuseppe’s Talk

May 31, 2008 - 12:09 pm - by Santo Leto

Yesterday, at the meeting with Marten Mickos and the Italian Team of SUN | MySQL in Rome, Giuseppe had a talk about the MySQL® Community.

If you are a newbie and you want to learn more about the fabulous MySQL® Community, please check this page the next week for his presentation!

Yo, don’t forget the MySQL® Magazine Survey:

  1. proposal: http://www.paragon-cs.com/wordpress/2008/05/26/mysql-survey-online/
  2. update: http://www.paragon-cs.com/wordpress/2008/05/28/mysql-survey-update/
  3. take it now: http://www.kwiksurveys.com/online-survey.php?surveyID=KOKK_e414c40b

Back home after the meeting in Rome with Marten Mickos

May 31, 2008 - 12:07 pm - by Santo Leto

Great conference yesterday at “La Sapienza” University in Rome with Marten Mickos and the Italian Team of Sun | MySQL.

I’ve just returned in Triest, my hometown, after 8 hours :( train ride.

Slides should be available the next week, here.

Marten, thank you for coming, I hope to see you in Italy once again!


Coming to Rome - May 30 2008

May 22, 2008 - 11:45 am - by Santo Leto

I will be in Rome on May 30 to attend the meeting with Marten Mickos.
Giuseppe has posted a translation of the official announcement of the event, here.

I will be there as a member of the Community and as CTO of HoneySoftware (an Italian ISV, MySQL® Enterprise Ready Partner).

I am wondering if there will be also a meeting in the morning with customers (as Giuseppe posted) or not: the official agenda starts only at 4:30 pm.

See you there!


Hello Planet MySQL®!

May 22, 2008 - 11:22 am - by Santo Leto

This is my first post on Planet MySQL® (a feed aggregator for blogs, news and opinions on MySQL®).

Latest posts you could be interested in:

  1. [More on Bug #29768]: It seem that Bug #29768 has been fixed with version 5.1.24-rc 
  2. [Server Monitoring]: Hit Ratios for MySQL® Server Monitoring: a SQL Script
  3. [Falcon Engine]: Re: Weekly Falcon Test Overview 2008-04-25 

Other resources:

  1. read more about me, here 
  2. learn more on the projects I am involved with, here 
     

Thank you for existing, I’m a Planet-dependent! ;-)


Trip to Pula: May 11 2008

May 18, 2008 - 4:56 pm - by Santo Leto

Last Sunday I was in Pula, the largest city in Istria, Croatia.

T’was a one day trip; Pula is about 110 Km far from Trieste.
I was there with my friends Perla, Michele, Igor, Barbara and Sara.

I’ve uploaded few photos on Flickr®, here - I will upload the entire set during the next weeks (I am waiting for a new ADSL line - I’m now using GPRS).

Roman Arena in Pula


Hit Ratios for MySQL® Server Monitoring: a SQL Script

May 3, 2008 - 2:21 am - by Santo Leto

information_schema.global_variables and information_schema.global_status are two useful tables for getting information on the MySQL® server configuration and status. They have been introduced in MySQL® version 5.1.

You know that some status variables are ‘raw’ and they need a little manipulation to bring a kind of useful information. For example, let’s consider the variable BYTES_RECEIVED (i.e. the number of bytes received from all clients).

If you just select that variable you don’t have a useful information, but if you calculate the ratio ‘Bytes Received per Second’

(`BYTES_RECEIVED`) / (`UPTIME`)

you have a more interesting value and you can see how this value is changing over time.

I’ve created a SQL Script that can help you calculate many interesting Hit Ratios and Derived Performance Metrics and I am posting it here so that you can have and idea on what ratios you can calculate to monitoring Server’s performance.

A similar Script is included in HoneyMonitor - Audit Pro Edition (there, all the Hit Ratios are calculated at a fixed interval - using a Scheduled Event - so that you can create several reports to view how that ratios are changing, say, hour after hour. Also you can see the Ratios ‘on-line’ just opening the Performance Tuning Monitor included in that Edition of HoneyMonitor).

The link for the download of the script is dpm-query-05-rc.zip (md5: 9c40109ac8266ec86cc0efb88fd580bb).

Here’s the script output and some screenshots of the Script Execution in HoneyMonitor for MySQL® 5.1.24-rc, 5.1.23-maria-preview-alpha and 6.0.4-alpha.

                               Falcon_Cache_Hit_Ratio: 99.961663418
                           Maria_Page_Cache_Hit_Ratio: NULL
              Maria_Page_Cache-Size_Pseudo_Efficiency: NULL
                         Maria_Key_Buffer_Blocks_Numb: NULL
                            Max_Maria_Page_Cache_Used: NULL
                       Current_Maria_Page_Cache_Usage: NULL
                         Maria_Page_Cache_Write_Ratio: NULL
                          InnoDB_Rows_Read_per_Second: 0.00512412757310717
                      InnoDB_Rows_Inserted_per_Second: 0.000677327207939453
                       InnoDB_Rows_Updated_per_Second: 0
                       InnoDB_Rows_Deleted_per_Second: 0
                      InnoDB_Pages_Created_per_Second: 0.00223812468710428
                         InnoDB_Pages_Read_per_Second: 0.00241481874134935
                      InnoDB_Pages_Written_per_Second: 0.0234414111965132
                         InnoDB_Data_Reads_per_Second: 0.00353388108490149
                        InnoDB_Data_Writes_per_Second: 0.0291839679594782
                        InnoDB_Data_Fsyncs_per_Second: 0.00774508937774244
                 InnoDB_Data_Pending_Reads_per_Second: 0
                InnoDB_Data_Pending_Writes_per_Second: 0
                InnoDB_Data_Pending_Fsyncs_per_Second: 0
          InnoDB_Buffer_Pool_Read_Requests_per_Second: 7.13561268663309
                  InnoDB_Buffer_Pool_Reads_per_Second: 0.00108961333451129
         InnoDB_Buffer_Pool_Read_Ahaed_Rnd_per_Second: 0.000117796036163383
         InnoDB_Buffer_Pool_Read_Ahaed_Seq_per_Second: 8.83470271225373e-005
         InnoDB_Buffer_Pool_Write_Requests_per_Second: 3.82734045999352
          InnoDB_Buffer_Pool_Pages_Flushed_per_Second: 0.0234414111965132
                     InnoDB_Row_Lock_Waits_per_Second: 0
                         InnoDB_Buffer_Pool_Hit_Ratio: 99.9847299260433
                               InnoDB_Page_Cache_Free: 68.9453125
                              InnoDB_Page_Cache_Usage: 31.0546875
                        InnoDB_Buffer_Pool_Pages_Free: 5783552
              InnoDB_Buffer_Pool_Pages_Free_per_Total: 68.9453125
                        InnoDB_Buffer_Pool_Pages_Data: 2588672
              InnoDB_Buffer_Pool_Pages_Data_per_Total: 30.859375
                       InnoDB_Buffer_Pool_Pages_Dirty: 409600
              InnoDB_Buffer_Pool_Pages_Dirty_per_Data: 15.8227848101266
                       InnoDB_Buffer_Pool_Pages_Clean: 2179072
              InnoDB_Buffer_Pool_Pages_Clean_per_Data: 84.1772151898734
                        InnoDB_Buffer_Pool_Pages_Misc: 16384
              InnoDB_Buffer_Pool_Pages_Misc_per_Total: 0.1953125
                     InnoDB_Buffer_Pool_Pages_Latched: 0
           InnoDB_Buffer_Pool_Pages_Latched_per_Total: 0
                          MyISAM_Key_Buffer_Hit_Ratio: 84.8989298454221
                               MyISAM_Lock_Contention: 0
                  MyISAM_Cache-Size_Pseudo_Efficiency: 11.3475177304965
                               Key_Buffer_Blocks_Numb: 16
                           Max_MyISAM_Key_Buffer_Used: 50
                      Current_MyISAM_Key_Buffer_Usage: 31.25
                               MyISAM_Key_Write_Ratio: 41.4893617021277
                           Aborted_Clients_per_Second: 0.000235592072326766
                       Aborted_Clients_per_Connection: 0.0666666666666667
                          Aborted_Connects_per_Second: 0
                            Bytes_Received_per_Second: 31.0664958624142
                      Aborted_Connects_per_Connection: 0
                        Bytes_Received_per_Connection: 8791.04166666667
                                Bytes_Sent_per_Second: 39.8645345584121
                            Bytes_Sent_per_Connection: 11280.6666666667
                                 Sort_Scan_per_Second: 0
                                Sort_Range_per_Second: 0
                         Sort_Merge-Passes_per_Second: 0
                                 Sort_Rows_per_Second: 0
                               Select_Scan_per_Second: 0.017374915334099
                               Select_Scan_per_Select: 125
                              Select_Range_per_Second: 0
                              Select_Range_per_Select: 0
                          Select_Full-Join_per_Second: 0
                          Select_Full-Join_per_Select: 0
                        Select_Range-Check_per_Second: 0
                        Select_Range-Check_per_Select: 0
                    Select_Full-Range-Join_per_Second: 0
                    Select_Full-Range-Join_per_Select: 0
                              Slow_Queries_per_Second: 0
                              Slow_Threads_per_Second: 0
                                Query_Cache_Hit_Ratio: 0
             Query_Cache_Hits_per_Query_Cache_Inserts: NULL
             Query_Cache_Low-Memory_Prunes_per_Second: 0
                              Query_Cache_Utilization: NULL
                     Query_Cache_Memory_Fragmentation: NULL
                                Temporary_Table_Ratio: 27.0181219110379
                 Temporary_In-Memory_Table_per_Second: 0.0715021939511735
Query_Cache_Inserts_per_Query_Cache_Low-Memory_Prunes: NULL
                      Temporary_Disk_Table_per_Second: 0.0193185499307948
                           Temporary_Files_per_Second: 0.000147245045204229
                                     Read_Write_Ratio: 20.5217391304348
                         Average_Table_Scan_Hit_Ratio: 100
                      s_COM_ADMIN_COMMANDS_per_Second: 0.00568365874488323
                            s_COM_ALTER_DB_per_Second: 0
                         s_COM_ALTER_EVENT_per_Second: 8.83470271225373e-005
                         s_COM_ALTER_TABLE_per_Second: 0
                             s_COM_ANALYZE_per_Second: 0
                               s_COM_BEGIN_per_Second: 0
                      s_COM_CALL_PROCEDURE_per_Second: 0.000795123244102836
                           s_COM_CHANGE_DB_per_Second: 0.00368112613010572
                       s_COM_CHANGE_MASTER_per_Second: 0
                               s_COM_CHECK_per_Second: 0
                            s_COM_CHECKSUM_per_Second: 0
                              s_COM_COMMIT_per_Second: 0
                        s_COM_CREATE_EVENT_per_Second: 0.00020614306328592
                           s_COM_CREATE_DB_per_Second: 0.000353388108490149
                     s_COM_CREATE_FUNCTION_per_Second: 0
                        s_COM_CREATE_INDEX_per_Second: 0
                        s_COM_CREATE_TABLE_per_Second: 0.000353388108490149
                         s_COM_CREATE_USER_per_Second: 0
                         s_COM_DEALLOC_SQL_per_Second: 0.00150189946108313
                              s_COM_DELETE_per_Second: 0
                        s_COM_DELETE_MULTI_per_Second: 0
                                  s_COM_DO_per_Second: 0
                             s_COM_DROP_DB_per_Second: 0.000265041081367612
                          s_COM_DROP_EVENT_per_Second: 0.000176694054245075
                       s_COM_DROP_FUNCTION_per_Second: 0.00106016432547045
                          s_COM_DROP_INDEX_per_Second: 0
                          s_COM_DROP_TABLE_per_Second: 0.000294490090408458
                           s_COM_DROP_USER_per_Second: 0
                         s_COM_EXECUTE_SQL_per_Second: 0.00150189946108313
                               s_COM_FLUSH_per_Second: 0
                               s_COM_GRANT_per_Second: 0
                            s_COM_HA_CLOSE_per_Second: 0
                             s_COM_HA_OPEN_per_Second: 0
                             s_COM_HA_READ_per_Second: 0
                                s_COM_HELP_per_Second: 0
                              s_COM_INSERT_per_Second: 0.000677327207939453
                       s_COM_INSERT_SELECT_per_Second: 0
                                s_COM_KILL_per_Second: 0
                                s_COM_LOAD_per_Second: 0
                         s_COM_LOCK_TABLES_per_Second: 0
                            s_COM_OPTIMIZE_per_Second: 0
                        s_COM_PRELOAD_KEYS_per_Second: 0
                         s_COM_PREPARE_SQL_per_Second: 0.00150189946108313
                               s_COM_PURGE_per_Second: 0
                   s_COM_PURGE_BEFORE_DATE_per_Second: 0
                        s_COM_RENAME_TABLE_per_Second: 0
                              s_COM_REPAIR_per_Second: 0
                             s_COM_REPLACE_per_Second: 0
                      s_COM_REPLACE_SELECT_per_Second: 0
                               s_COM_RESET_per_Second: 0
                              s_COM_REVOKE_per_Second: 0
                          s_COM_REVOKE_ALL_per_Second: 0
                            s_COM_ROLLBACK_per_Second: 0
                           s_COM_SAVEPOINT_per_Second: 0
                              s_COM_SELECT_per_Second: 0.0138999322672792
                          s_COM_SET_OPTION_per_Second: 0.00859911063992697
                  s_COM_SHOW_BINLOG_EVENTS_per_Second: 0
                        s_COM_SHOW_BINLOGS_per_Second: 0
                       s_COM_SHOW_CHARSETS_per_Second: 8.83470271225373e-005
                     s_COM_SHOW_COLLATIONS_per_Second: 0
                   s_COM_SHOW_COLUMN_TYPES_per_Second: 0
                      s_COM_SHOW_CREATE_DB_per_Second: 0
                   s_COM_SHOW_CREATE_EVENT_per_Second: 0.00020614306328592
                   s_COM_SHOW_CREATE_TABLE_per_Second: 5.88980180816916e-005
                      s_COM_SHOW_DATABASES_per_Second: 0.000235592072326766
                    s_COM_SHOW_ENGINE_LOGS_per_Second: 0
                  s_COM_SHOW_ENGINE_STATUS_per_Second: 0
                         s_COM_SHOW_ERRORS_per_Second: 0
                         s_COM_SHOW_EVENTS_per_Second: 0.000353388108490149
                         s_COM_SHOW_FIELDS_per_Second: 2.94490090408458e-005
                         s_COM_SHOW_GRANTS_per_Second: 0
                           s_COM_SHOW_KEYS_per_Second: 2.94490090408458e-005
                  s_COM_SHOW_MASTER_STATUS_per_Second: 0
                     s_COM_SHOW_NEW_MASTER_per_Second: 0
                    s_COM_SHOW_OPEN_TABLES_per_Second: 0
                        s_COM_SHOW_PLUGINS_per_Second: 0
                   s_COM_SHOW_ENGINE_MUTEX_per_Second: 0
                     s_COM_SHOW_PRIVILEGES_per_Second: 0.000176694054245075
                    s_COM_SHOW_PROCESSLIST_per_Second: 0
                    s_COM_SHOW_SLAVE_HOSTS_per_Second: 0
                   s_COM_SHOW_SLAVE_STATUS_per_Second: 0
                         s_COM_SHOW_STATUS_per_Second: 0
                s_COM_SHOW_STORAGE_ENGINES_per_Second: 0
                         s_COM_SHOW_TABLES_per_Second: 0.000294490090408458
                       s_COM_SHOW_TRIGGERS_per_Second: 0
                      s_COM_SHOW_VARIABLES_per_Second: 0.000265041081367612
                       s_COM_SHOW_WARNINGS_per_Second: 0
                         s_COM_SLAVE_START_per_Second: 0
                          s_COM_SLAVE_STOP_per_Second: 0
                          s_COM_STMT_CLOSE_per_Second: 0.00126630738875637
                          s_COM_STMT_FETCH_per_Second: 0
                          s_COM_STMT_RESET_per_Second: 0
                            s_COM_TRUNCATE_per_Second: 0.000382837117530995
                              s_COM_UPDATE_per_Second: 0
                       s_COM_UNLOCK_TABLES_per_Second: 0
                        s_COM_UPDATE_MULTI_per_Second: 0
                           s_COM_XA_COMMIT_per_Second: 0
                              s_COM_XA_END_per_Second: 0
                          s_COM_XA_PREPARE_per_Second: 0
                          s_COM_XA_RECOVER_per_Second: 0
                         s_COM_XA_ROLLBACK_per_Second: 0
                            s_COM_XA_START_per_Second: 0
                        s_COM_STMT_PREPARE_per_Second: 0.00150189946108313
                 s_COM_STMT_SEND_LONG_DATA_per_Second: 0
                        s_COM_STMT_EXECUTE_per_Second: 0.00126630738875637
                            s_COM_ROLLBACK_per_Second: 0
                       s_COM_UNLOCK_TABLES_per_Second: 0
                          s_FLUSH_COMMANDS_per_Second: 2.94490090408458e-005
                     s_PREPARED_STMT_COUNT_per_Second: 0
                       Maximum_Connection_Utilization: 4.63576158940397
                               Connection_Utilization: 4.63576158940397
                       Connection_Attempts_per_Second: 0.00353388108490149
                                   Threads_per_Second: 0.00306269694024796
                               Thread_Cache_Miss_Rate: 86.6666666666667
                              Thread_Cache_Efficiency: 13.3333333333333
                             Thread_Cache_Utilization: NULL
                             Opened_Tables_per_Second: 0.0533616043820125
                             Tables_Cache_Utilization: 100
                                 XACommits_per_Second: 0
                             XARollbacks_per_XACommit: NULL
                          Average_XA_Transaction_Size: NULL
                                 Inserts_per_XACommit: NULL
                                   Commits_per_Second: 0
                                 Rollbacks_per_Commit: NULL
                             Average_Transaction_Size: NULL
                                   Inserts_per_Commit: NULL
                                  Question_per_Second: 3.33353947639662
                                   Queries_per_Second: 0.0145772594752187
                                   Selects_per_Second: 0.0138999322672792
                                   Inserts_per_Second: 0.000677327207939453
                                   Updates_per_Second: 0
                                   Deletes_per_Second: 0
                                  Replaces_per_Second: 0
                              Question_per_Connection: 943.308333333333
                               Queries_per_Connection: 4.125
                               Selects_per_Connection: 3.93333333333333
                               Inserts_per_Connection: 0.191666666666667
                               Updates_per_Connection: 0
                               Deletes_per_Connection: 0
                              Replaces_per_Connection: 0
                              Binlog_Cache_Contention: NULL

script_output_5124.jpgscript_output_5123-maria.jpgscript_output_6004.jpg


It seem that Bug #29768 has been fixed with version 5.1.24-rc

May 2, 2008 - 9:52 am - by Santo Leto

On July 12 2007 I posted Bug #29768 - ‘ALTER EVENT .. RENAME TO .. drops the event if event_scheduler is ON’ - for MySQL® 5.1.20-beta and Miguel verified it one hour after my post with MySQL® 5.1.21-beta.

Some months later, on Oct 19 2007, Damien cannot reproduce that bug with the latest versions 5.1.23-rc and 5.2.6-alpha, but unfortunately I was still able to reproduce it with version 5.1.23-rc, as I posted on Feb 16 2008.

Now it seem that I can’t reproduce it with the new 5.1.24-rc. Maybe it has been fixed by fixing other bugs. The problem is that I am still able to reproduce it with version 6.0.4-alpha.

Just to summarize:
5.1.23-rc - VERIFIED
5.1.24-rc - CAN’T REPEAT
6.0.4-alpha - VERIFIED

What do you think? What about version 6.0.5-alpha?
Here’s the exact Script for reproducing it with old versions of the Server, as Miguel commented on July 12 2007:

DROP DATABASE IF EXISTS event_test;
CREATE DATABASE event_test;
USE event_test;
SET GLOBAL event_scheduler = ‘OFF’;
delimiter $$
CREATE DEFINER = ‘root’@'localhost’ EVENT  `event_test`.`at_event` ON SCHEDULE AT
CURRENT_TIMESTAMP ON COMPLETION PRESERVE ENABLE DO
BEGIN
 #do nothing
END$$
delimiter ;
SHOW EVENTS FROM `event_test`\G
SET GLOBAL event_scheduler=’ON’;
ALTER EVENT `event_test`.`at_event` RENAME TO `event_test`.`at_event2`;
SHOW EVENTS FROM `event_test`\G

And here’s the script output:

5.1.23-rc - VERIFIED

mysql> DROP DATABASE IF EXISTS event_test;
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> CREATE DATABASE event_test;
Query OK, 1 row affected (0.00 sec)

mysql> USE event_test;
Database changed
mysql> SET GLOBAL event_scheduler = ‘OFF’;
Query OK, 0 rows affected (0.00 sec)

mysql> delimiter $$
mysql> CREATE DEFINER = ‘root’@'localhost’ EVENT  `event_test`.`at_event` ON SCH
EDULE AT
    -> CURRENT_TIMESTAMP ON COMPLETION PRESERVE ENABLE DO
    -> BEGIN
    ->  #do nothing
    -> END$$
Query OK, 0 rows affected (0.00 sec)

mysql> delimiter ;
mysql> SHOW EVENTS FROM `event_test`\G
*************************** 1. row ***************************
                  Db: event_test
                Name: at_event
             Definer: root@localhost
           Time zone: SYSTEM
                Type: ONE TIME
          Execute at: 2008-05-02 09:14:23
      Interval value: NULL
      Interval field: NULL
              Starts: NULL
                Ends: NULL
              Status: ENABLED
          Originator: 1
character_set_client: latin1
collation_connection: latin1_swedish_ci
  Database Collation: latin1_swedish_ci
1 row in set (0.02 sec)

mysql> SET GLOBAL event_scheduler=’ON’;
Query OK, 0 rows affected (0.00 sec)

mysql> ALTER EVENT `event_test`.`at_event` RENAME TO `event_test`.`at_event2`;
Query OK, 0 rows affected (0.00 sec)

mysql> SHOW EVENTS FROM `event_test`\G
Empty set (0.02 sec)

mysql>

5.1.24-rc - CAN’T REPEAT

mysql> DROP DATABASE IF EXISTS event_test;
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> CREATE DATABASE event_test;
Query OK, 1 row affected (0.00 sec)

mysql> USE event_test;
Database changed
mysql> SET GLOBAL event_scheduler = ‘OFF’;
Query OK, 0 rows affected (0.00 sec)

mysql> delimiter $$
mysql> CREATE DEFINER = ‘root’@'localhost’ EVENT  `event_test`.`at_event` ON SCH
EDULE AT
    -> CURRENT_TIMESTAMP ON COMPLETION PRESERVE ENABLE DO
    -> BEGIN
    ->  #do nothing
    -> END$$
Query OK, 0 rows affected (0.03 sec)

mysql> delimiter ;
mysql> SHOW EVENTS FROM `event_test`\G
*************************** 1. row ***************************
                  Db: event_test
                Name: at_event
             Definer: root@localhost
           Time zone: SYSTEM
                Type: ONE TIME
          Execute at: 2008-05-02 09:13:26
      Interval value: NULL
      Interval field: NULL
              Starts: NULL
                Ends: NULL
              Status: ENABLED
          Originator: 1
character_set_client: latin1
collation_connection: latin1_swedish_ci
  Database Collation: latin1_swedish_ci
1 row in set (0.00 sec)

mysql> SET GLOBAL event_scheduler=’ON’;
Query OK, 0 rows affected (0.00 sec)

mysql> ALTER EVENT `event_test`.`at_event` RENAME TO `event_test`.`at_event2`;
Query OK, 0 rows affected (0.00 sec)

mysql> SHOW EVENTS FROM `event_test`\G
*************************** 1. row ***************************
                  Db: event_test
                Name: at_event2
             Definer: root@localhost
           Time zone: SYSTEM
                Type: ONE TIME
          Execute at: 2008-05-02 09:13:26
      Interval value: NULL
      Interval field: NULL
              Starts: NULL
                Ends: NULL
              Status: ENABLED
          Originator: 1
character_set_client: latin1
collation_connection: latin1_swedish_ci
  Database Collation: latin1_swedish_ci
1 row in set (0.00 sec)

mysql>

6.0.4-alpha - VERIFIED

mysql> DROP DATABASE IF EXISTS event_test;
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> CREATE DATABASE event_test;
Query OK, 1 row affected (0.00 sec)

mysql> USE event_test;
Database changed
mysql> SET GLOBAL event_scheduler = ‘OFF’;
Query OK, 0 rows affected (0.00 sec)

mysql> delimiter $$
mysql> CREATE DEFINER = ‘root’@'localhost’ EVENT  `event_test`.`at_event` ON SCH
EDULE AT
    -> CURRENT_TIMESTAMP ON COMPLETION PRESERVE ENABLE DO
    -> BEGIN
    ->  #do nothing
    -> END$$
Query OK, 0 rows affected (0.03 sec)

mysql> delimiter ;
mysql> SHOW EVENTS FROM `event_test`\G
*************************** 1. row ***************************
                  Db: event_test
                Name: at_event
             Definer: root@localhost
           Time zone: SYSTEM
                Type: ONE TIME
          Execute at: 2008-05-02 09:28:19
      Interval value: NULL
      Interval field: NULL
              Starts: NULL
                Ends: NULL
              Status: ENABLED
          Originator: 1
character_set_client: latin1
collation_connection: latin1_swedish_ci
  Database Collation: latin1_swedish_ci
1 row in set (0.00 sec)

mysql> SET GLOBAL event_scheduler=’ON’;
Query OK, 0 rows affected (0.00 sec)

mysql> ALTER EVENT `event_test`.`at_event` RENAME TO `event_test`.`at_event2`;
Query OK, 0 rows affected (0.02 sec)

mysql> SHOW EVENTS FROM `event_test`\G
Empty set (0.02 sec)

mysql>


My (Italian) word of the last months is ‘Sconvolgente’, wanna know why?

May 2, 2008 - 12:10 am - by Santo Leto

2008 was announced as the year of the *change*.

On February I started work on performance tuning features and I planned those two new Editions of HoneyMonitor (Pro and Audit Pro).

On March I returned back to Trieste - my University town - after a two-year-full-immersion experience at HoneySoftware, in Caltagirone, where I forgot all the job-not-related aspects of the human life.

On April, meeting my (old and new) friends, going to cinema and doing things like those, I recovered my social life.

I removed the password protection from my blog, I announced HoneyMonitor Audit Pro (publishing 150+ screenshots of that Edition), I removed some out-of-date pages of our site and, yes, I got my first MySQL® not-a-bug.

I also have changed my residence, make my hair shorter and bought new glasses.

;-)

Now, the real question is: what does it mean ’sconvolgente’? and why ’sconvolgente’?

Here’s some reasons for the ‘upsetting’ word.

On January 16 Sun acquires MySQL AB for 1B USD. That news upset me.

A night, on February, I created this image, and it upset me {How many line of code have you ever wrote for just an image you have created after dinner :( ?}.

‘Santo, you upset me’, said R. - again and again - few weeks ago after she talked with me for about 8 hours, till 8 A.M., about all you can talk over with a girl the first time you meet her.

‘Santo, I’m upset’, said F. after he saw the new Home Page (he was referring to the new ‘Audit Pro’ screenshots and the new HoneyMonitor Features Matrix).

So, after all I can really say that ‘upsetting’ was a recurring word of the last months ;-)

May and June, what are you reserving to me? Marten, maybe…do you plan to have another Mike Zinner in 2008  :)  ?