- developers - lists.mariadb.org

[Maria-developers] WL enhancements
by Sergei Golubchik 17 Mar '10

17 Mar '10

Hi. That's a rough list of enhancement ideas for worklog. Some of them I'm going to do (but not all). Feel free to suggest more or "get rid of WL, use X instead", just don't forget the "because of" part. report: easy to do tasks make it to provide a list of "low-handing fruits", tasks that could be done relatively easily and without prior extensive MySQL source knowledge. For community members that want to help. report: who's doing what NOW that's pretty obvious report: tasks for specific version, roadmap worklog kind of does it now, mostly listed for completeness ability to remove hours Somebody mentioned that a number of hours could be increased by mistake, and there should be a way to decrease is back. I'm not convinced it's a good idea, though. generate weekly report templates to reduce the need for double or tripple reporting. WL generates a weekly report for a developer, based on its data, and sends it to this developer. The developer in question can edit it and sent to reports@, or copy-paste from it, or filter it out and ignore completely. private tasks and categories There should be a way to have private categories and tasks in WL. this includes fixing "private" field in WL tasks. distingushing between employees and users for many tasks from the above WL needs to distinguish between MPAB employees and other registered users. better search Sanja seems to be unhappy with WL search make it more readable for novice wl readers no big redesign or anything, though. but I think that moving task description up and, say, attached files and estimated number of hours down could help somewhat. not editable unless authenticated that's more a bug than a new feature. no changes in tasks should be allowed unless a user is authenticated. subscribe w/o authentication but perhaps we may want to allow users to subscribe to tasks w/o being authenticated ? I'm not going to do that, though. embeddable views a couple of pages that could be easily inserted (iframe-ed ?) into other pages without disrupting the design too much. Mainly "roadmap" and "easy tasks" reports, but also "WL of the day" too. "WL of the day" - it's a new crazy idea, I wanted to discuss. Basically, that's a small block somewhere on the main page that shows a randomly (?) selected WL task - only the description (or a part of it), a link to a full task page, and voting controls (useless... very important). Regards, Sergei

6 10

[Maria-developers] bzr commit into Mariadb 5.2, with Maria 2.0:maria/5.2 branch (igor:2744) Bug#539643
by Igor Babaev 17 Mar '10

17 Mar '10

#At lp:maria/5.2 based on revid:sergii@pisem.net-20100315115123-21tgprclhz7qbk6m 2744 Igor Babaev 2010-03-16 Fixed bug #539643. The cause of the problem is a bad merge MariaDB-5.1=>MariaDB-5.2. Added the vcol suite to the list of the default suites run by mysql-test-run.pl. modified: mysql-test/mysql-test-run.pl mysql-test/suite/vcol/r/vcol_supported_sql_funcs_innodb.result mysql-test/suite/vcol/r/vcol_supported_sql_funcs_myisam.result sql/field.cc === modified file 'mysql-test/mysql-test-run.pl' --- a/mysql-test/mysql-test-run.pl 2010-03-10 10:32:14 +0000 +++ b/mysql-test/mysql-test-run.pl 2010-03-17 02:32:31 +0000 @@ -126,7 +126,7 @@ my $path_config_file; # The ge # executables will be used by the test suite. our $opt_vs_config = $ENV{'MTR_VS_CONFIG'}; -my $DEFAULT_SUITES= "main,binlog,federated,rpl,maria,parts"; +my $DEFAULT_SUITES= "main,binlog,federated,rpl,maria,parts,vcol"; my $opt_suites; our $opt_verbose= 0; # Verbose output, enable with --verbose === modified file 'mysql-test/suite/vcol/r/vcol_supported_sql_funcs_innodb.result' --- a/mysql-test/suite/vcol/r/vcol_supported_sql_funcs_innodb.result 2009-10-16 22:57:48 +0000 +++ b/mysql-test/suite/vcol/r/vcol_supported_sql_funcs_innodb.result 2010-03-17 02:32:31 +0000 @@ -2205,7 +2205,7 @@ t1 CREATE TABLE `t1` ( insert into t1 values (1196440219,default); select * from t1; a b -1196440219 2007-11-30 19:30:19 +1196440219 2007-11-30 08:30:19 drop table t1; set sql_warnings = 0; # GET_FORMAT() === modified file 'mysql-test/suite/vcol/r/vcol_supported_sql_funcs_myisam.result' --- a/mysql-test/suite/vcol/r/vcol_supported_sql_funcs_myisam.result 2009-10-16 22:57:48 +0000 +++ b/mysql-test/suite/vcol/r/vcol_supported_sql_funcs_myisam.result 2010-03-17 02:32:31 +0000 @@ -2205,7 +2205,7 @@ t1 CREATE TABLE `t1` ( insert into t1 values (1196440219,default); select * from t1; a b -1196440219 2007-11-30 19:30:19 +1196440219 2007-11-30 08:30:19 drop table t1; set sql_warnings = 0; # GET_FORMAT() === modified file 'sql/field.cc' --- a/sql/field.cc 2010-03-15 11:51:23 +0000 +++ b/sql/field.cc 2010-03-17 02:32:31 +0000 @@ -9598,13 +9598,13 @@ bool Create_field::init(THD *thd, char * interval_list.empty(); comment= *fld_comment; + vcol_info= fld_vcol_info; stored_in_db= TRUE; /* Initialize data for a computed field */ if ((uchar)fld_type == (uchar)MYSQL_TYPE_VIRTUAL) { DBUG_ASSERT(vcol_info && vcol_info->expr_item); - vcol_info= fld_vcol_info; stored_in_db= vcol_info->is_stored(); /* Walk through the Item tree checking if all items are valid @@ -9624,8 +9624,6 @@ bool Create_field::init(THD *thd, char * */ sql_type= fld_type= vcol_info->get_real_type(); } - else - vcol_info= NULL; /* Set NO_DEFAULT_VALUE_FLAG if this field doesn't have a default value and

1 0

[Maria-developers] Updated (by Serg): Phone home (12)
by worklog-noreply＠askmonty.org 16 Mar '10

16 Mar '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Phone home CREATION DATE..: Wed, 01 Apr 2009, 15:30 SUPERVISOR.....: Knielsen IMPLEMENTOR....: Bothorsen COPIES TO......: Sergei CATEGORY.......: Server-RawIdeaBin TASK ID........: 12 (http://askmonty.org/worklog/?tid=12) VERSION........: Connector/.NET-1.6 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 120 (hours remain) ORIG. ESTIMATE.: 120 PROGRESS NOTES: -=-=(Serg - Tue, 16 Mar 2010, 19:51)=-=- Observers changed: Sergei -=-=(Monty - Tue, 09 Mar 2010, 19:28)=-=- High Level Description modified. --- /tmp/wklog.12.old.27527 2010-03-09 19:28:51.000000000 +0000 +++ /tmp/wklog.12.new.27527 2010-03-09 19:28:51.000000000 +0000 @@ -2,10 +2,10 @@ a "phone home" feature. When this plugin is installed, the database server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and -analysis of this information will give MySQL AB useful insight into +analysis of this information will give MariaDB developers useful insight into the user base -Summary of collected information +Summary of collected information (that anyone will be allowed to access) how many servers are running the plugin - can help estimate total number of running servers worldwide what platform & hardware they are running on @@ -28,7 +28,7 @@ gives among other things, the MySQL server version & Server uptime (optionally by user) geographic location (optionally by user) user information / company name - (optionally by user) MySQL customer support contract id + (optionally by user) Monty Program Ab customer support contract id Data Not Sent Contents or names of any user database -=-=(Monty - Tue, 09 Mar 2010, 19:25)=-=- High Level Description modified. --- /tmp/wklog.12.old.27502 2010-03-09 19:25:56.000000000 +0000 +++ /tmp/wklog.12.new.27502 2010-03-09 19:25:56.000000000 +0000 @@ -1,6 +1,6 @@ -This project is to develop a plugin for the MySQL server that provides +This project is to develop a plugin for the MariaDB server that provides a "phone home" feature. When this plugin is installed, the database -server will regularly contact a web service operated by MySQL AB, and +server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and analysis of this information will give MySQL AB useful insight into the user base @@ -32,10 +32,10 @@ Data Not Sent Contents or names of any user database - Anything that allows MySQL to track down the user + Anything that allows MariaDB to track down the user if the user doesn't explicitly permit it -What will run at MySQL's datacenter +What will run at Monty Program's or/and the users datacenter simple CGI on Apache takes a HTTP REST PUT insert received information into a database DESCRIPTION: This project is to develop a plugin for the MariaDB server that provides a "phone home" feature. When this plugin is installed, the database server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and analysis of this information will give MariaDB developers useful insight into the user base Summary of collected information (that anyone will be allowed to access) how many servers are running the plugin - can help estimate total number of running servers worldwide what platform & hardware they are running on what version and build they are running what features are being used Information sent from each instance A unique server identifier secure hash of MAC address + listening port unique, but doesn't leak customer data Processor type, speed, processor count / core count, bitwidth (32/64) OS / Distro / Kernel id and version Which storage engines are in use Number and size of databases (disk space, probably can't for cluster) Counts / Rates of I/O activity List of loaded plugins SHOW STATUS SHOW VARIABLES (but not anything that can give away user identity) will be a explicit list of what variables will be shown gives among other things, the MySQL server version & Server uptime (optionally by user) geographic location (optionally by user) user information / company name (optionally by user) Monty Program Ab customer support contract id Data Not Sent Contents or names of any user database Anything that allows MariaDB to track down the user if the user doesn't explicitly permit it What will run at Monty Program's or/and the users datacenter simple CGI on Apache takes a HTTP REST PUT insert received information into a database database schema is TBD, but not complicated Analysis/Reporting/Business Process are TBD What will run on the users' machines Daemon Plugin module can be dynamically loaded, or statically compiled runs as part of the mysqld process daemon plugins have full access to server internals Start and use it's own thread will not block normal operation will yield often will hold read mutexs as short as possible Loop and delay on an interval (specified by option) probably default to be on server restart and about once a week randomly spread time to avoid too many calling in at the same moment Gather data from internal mysqld data structures Convert data into simple text format (human readable) Transmit data via HTTP REST POST to one or more given URLs ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Serg): Phone home (12)
by worklog-noreply＠askmonty.org 16 Mar '10

16 Mar '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Phone home CREATION DATE..: Wed, 01 Apr 2009, 15:30 SUPERVISOR.....: Knielsen IMPLEMENTOR....: Bothorsen COPIES TO......: Sergei CATEGORY.......: Server-RawIdeaBin TASK ID........: 12 (http://askmonty.org/worklog/?tid=12) VERSION........: Connector/.NET-1.6 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 120 (hours remain) ORIG. ESTIMATE.: 120 PROGRESS NOTES: -=-=(Serg - Tue, 16 Mar 2010, 19:51)=-=- Observers changed: Sergei -=-=(Monty - Tue, 09 Mar 2010, 19:28)=-=- High Level Description modified. --- /tmp/wklog.12.old.27527 2010-03-09 19:28:51.000000000 +0000 +++ /tmp/wklog.12.new.27527 2010-03-09 19:28:51.000000000 +0000 @@ -2,10 +2,10 @@ a "phone home" feature. When this plugin is installed, the database server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and -analysis of this information will give MySQL AB useful insight into +analysis of this information will give MariaDB developers useful insight into the user base -Summary of collected information +Summary of collected information (that anyone will be allowed to access) how many servers are running the plugin - can help estimate total number of running servers worldwide what platform & hardware they are running on @@ -28,7 +28,7 @@ gives among other things, the MySQL server version & Server uptime (optionally by user) geographic location (optionally by user) user information / company name - (optionally by user) MySQL customer support contract id + (optionally by user) Monty Program Ab customer support contract id Data Not Sent Contents or names of any user database -=-=(Monty - Tue, 09 Mar 2010, 19:25)=-=- High Level Description modified. --- /tmp/wklog.12.old.27502 2010-03-09 19:25:56.000000000 +0000 +++ /tmp/wklog.12.new.27502 2010-03-09 19:25:56.000000000 +0000 @@ -1,6 +1,6 @@ -This project is to develop a plugin for the MySQL server that provides +This project is to develop a plugin for the MariaDB server that provides a "phone home" feature. When this plugin is installed, the database -server will regularly contact a web service operated by MySQL AB, and +server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and analysis of this information will give MySQL AB useful insight into the user base @@ -32,10 +32,10 @@ Data Not Sent Contents or names of any user database - Anything that allows MySQL to track down the user + Anything that allows MariaDB to track down the user if the user doesn't explicitly permit it -What will run at MySQL's datacenter +What will run at Monty Program's or/and the users datacenter simple CGI on Apache takes a HTTP REST PUT insert received information into a database DESCRIPTION: This project is to develop a plugin for the MariaDB server that provides a "phone home" feature. When this plugin is installed, the database server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and analysis of this information will give MariaDB developers useful insight into the user base Summary of collected information (that anyone will be allowed to access) how many servers are running the plugin - can help estimate total number of running servers worldwide what platform & hardware they are running on what version and build they are running what features are being used Information sent from each instance A unique server identifier secure hash of MAC address + listening port unique, but doesn't leak customer data Processor type, speed, processor count / core count, bitwidth (32/64) OS / Distro / Kernel id and version Which storage engines are in use Number and size of databases (disk space, probably can't for cluster) Counts / Rates of I/O activity List of loaded plugins SHOW STATUS SHOW VARIABLES (but not anything that can give away user identity) will be a explicit list of what variables will be shown gives among other things, the MySQL server version & Server uptime (optionally by user) geographic location (optionally by user) user information / company name (optionally by user) Monty Program Ab customer support contract id Data Not Sent Contents or names of any user database Anything that allows MariaDB to track down the user if the user doesn't explicitly permit it What will run at Monty Program's or/and the users datacenter simple CGI on Apache takes a HTTP REST PUT insert received information into a database database schema is TBD, but not complicated Analysis/Reporting/Business Process are TBD What will run on the users' machines Daemon Plugin module can be dynamically loaded, or statically compiled runs as part of the mysqld process daemon plugins have full access to server internals Start and use it's own thread will not block normal operation will yield often will hold read mutexs as short as possible Loop and delay on an interval (specified by option) probably default to be on server restart and about once a week randomly spread time to avoid too many calling in at the same moment Gather data from internal mysqld data structures Convert data into simple text format (human readable) Transmit data via HTTP REST POST to one or more given URLs ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Serg): Phone home (12)
by worklog-noreply＠askmonty.org 16 Mar '10

16 Mar '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Phone home CREATION DATE..: Wed, 01 Apr 2009, 15:30 SUPERVISOR.....: Knielsen IMPLEMENTOR....: Bothorsen COPIES TO......: Sergei CATEGORY.......: Server-RawIdeaBin TASK ID........: 12 (http://askmonty.org/worklog/?tid=12) VERSION........: Connector/.NET-1.6 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 120 (hours remain) ORIG. ESTIMATE.: 120 PROGRESS NOTES: -=-=(Serg - Tue, 16 Mar 2010, 19:51)=-=- Observers changed: Sergei -=-=(Monty - Tue, 09 Mar 2010, 19:28)=-=- High Level Description modified. --- /tmp/wklog.12.old.27527 2010-03-09 19:28:51.000000000 +0000 +++ /tmp/wklog.12.new.27527 2010-03-09 19:28:51.000000000 +0000 @@ -2,10 +2,10 @@ a "phone home" feature. When this plugin is installed, the database server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and -analysis of this information will give MySQL AB useful insight into +analysis of this information will give MariaDB developers useful insight into the user base -Summary of collected information +Summary of collected information (that anyone will be allowed to access) how many servers are running the plugin - can help estimate total number of running servers worldwide what platform & hardware they are running on @@ -28,7 +28,7 @@ gives among other things, the MySQL server version & Server uptime (optionally by user) geographic location (optionally by user) user information / company name - (optionally by user) MySQL customer support contract id + (optionally by user) Monty Program Ab customer support contract id Data Not Sent Contents or names of any user database -=-=(Monty - Tue, 09 Mar 2010, 19:25)=-=- High Level Description modified. --- /tmp/wklog.12.old.27502 2010-03-09 19:25:56.000000000 +0000 +++ /tmp/wklog.12.new.27502 2010-03-09 19:25:56.000000000 +0000 @@ -1,6 +1,6 @@ -This project is to develop a plugin for the MySQL server that provides +This project is to develop a plugin for the MariaDB server that provides a "phone home" feature. When this plugin is installed, the database -server will regularly contact a web service operated by MySQL AB, and +server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and analysis of this information will give MySQL AB useful insight into the user base @@ -32,10 +32,10 @@ Data Not Sent Contents or names of any user database - Anything that allows MySQL to track down the user + Anything that allows MariaDB to track down the user if the user doesn't explicitly permit it -What will run at MySQL's datacenter +What will run at Monty Program's or/and the users datacenter simple CGI on Apache takes a HTTP REST PUT insert received information into a database DESCRIPTION: This project is to develop a plugin for the MariaDB server that provides a "phone home" feature. When this plugin is installed, the database server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and analysis of this information will give MariaDB developers useful insight into the user base Summary of collected information (that anyone will be allowed to access) how many servers are running the plugin - can help estimate total number of running servers worldwide what platform & hardware they are running on what version and build they are running what features are being used Information sent from each instance A unique server identifier secure hash of MAC address + listening port unique, but doesn't leak customer data Processor type, speed, processor count / core count, bitwidth (32/64) OS / Distro / Kernel id and version Which storage engines are in use Number and size of databases (disk space, probably can't for cluster) Counts / Rates of I/O activity List of loaded plugins SHOW STATUS SHOW VARIABLES (but not anything that can give away user identity) will be a explicit list of what variables will be shown gives among other things, the MySQL server version & Server uptime (optionally by user) geographic location (optionally by user) user information / company name (optionally by user) Monty Program Ab customer support contract id Data Not Sent Contents or names of any user database Anything that allows MariaDB to track down the user if the user doesn't explicitly permit it What will run at Monty Program's or/and the users datacenter simple CGI on Apache takes a HTTP REST PUT insert received information into a database database schema is TBD, but not complicated Analysis/Reporting/Business Process are TBD What will run on the users' machines Daemon Plugin module can be dynamically loaded, or statically compiled runs as part of the mysqld process daemon plugins have full access to server internals Start and use it's own thread will not block normal operation will yield often will hold read mutexs as short as possible Loop and delay on an interval (specified by option) probably default to be on server restart and about once a week randomly spread time to avoid too many calling in at the same moment Gather data from internal mysqld data structures Convert data into simple text format (human readable) Transmit data via HTTP REST POST to one or more given URLs ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Serg): Phone home (12)
by worklog-noreply＠askmonty.org 16 Mar '10

16 Mar '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Phone home CREATION DATE..: Wed, 01 Apr 2009, 15:30 SUPERVISOR.....: Knielsen IMPLEMENTOR....: Bothorsen COPIES TO......: Sergei CATEGORY.......: Server-RawIdeaBin TASK ID........: 12 (http://askmonty.org/worklog/?tid=12) VERSION........: Connector/.NET-1.6 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 120 (hours remain) ORIG. ESTIMATE.: 120 PROGRESS NOTES: -=-=(Serg - Tue, 16 Mar 2010, 19:51)=-=- Observers changed: Sergei -=-=(Monty - Tue, 09 Mar 2010, 19:28)=-=- High Level Description modified. --- /tmp/wklog.12.old.27527 2010-03-09 19:28:51.000000000 +0000 +++ /tmp/wklog.12.new.27527 2010-03-09 19:28:51.000000000 +0000 @@ -2,10 +2,10 @@ a "phone home" feature. When this plugin is installed, the database server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and -analysis of this information will give MySQL AB useful insight into +analysis of this information will give MariaDB developers useful insight into the user base -Summary of collected information +Summary of collected information (that anyone will be allowed to access) how many servers are running the plugin - can help estimate total number of running servers worldwide what platform & hardware they are running on @@ -28,7 +28,7 @@ gives among other things, the MySQL server version & Server uptime (optionally by user) geographic location (optionally by user) user information / company name - (optionally by user) MySQL customer support contract id + (optionally by user) Monty Program Ab customer support contract id Data Not Sent Contents or names of any user database -=-=(Monty - Tue, 09 Mar 2010, 19:25)=-=- High Level Description modified. --- /tmp/wklog.12.old.27502 2010-03-09 19:25:56.000000000 +0000 +++ /tmp/wklog.12.new.27502 2010-03-09 19:25:56.000000000 +0000 @@ -1,6 +1,6 @@ -This project is to develop a plugin for the MySQL server that provides +This project is to develop a plugin for the MariaDB server that provides a "phone home" feature. When this plugin is installed, the database -server will regularly contact a web service operated by MySQL AB, and +server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and analysis of this information will give MySQL AB useful insight into the user base @@ -32,10 +32,10 @@ Data Not Sent Contents or names of any user database - Anything that allows MySQL to track down the user + Anything that allows MariaDB to track down the user if the user doesn't explicitly permit it -What will run at MySQL's datacenter +What will run at Monty Program's or/and the users datacenter simple CGI on Apache takes a HTTP REST PUT insert received information into a database DESCRIPTION: This project is to develop a plugin for the MariaDB server that provides a "phone home" feature. When this plugin is installed, the database server will regularly contact a web service operated by Monty Program Ab, and upload a bundle of non-sensitive information. The collection and analysis of this information will give MariaDB developers useful insight into the user base Summary of collected information (that anyone will be allowed to access) how many servers are running the plugin - can help estimate total number of running servers worldwide what platform & hardware they are running on what version and build they are running what features are being used Information sent from each instance A unique server identifier secure hash of MAC address + listening port unique, but doesn't leak customer data Processor type, speed, processor count / core count, bitwidth (32/64) OS / Distro / Kernel id and version Which storage engines are in use Number and size of databases (disk space, probably can't for cluster) Counts / Rates of I/O activity List of loaded plugins SHOW STATUS SHOW VARIABLES (but not anything that can give away user identity) will be a explicit list of what variables will be shown gives among other things, the MySQL server version & Server uptime (optionally by user) geographic location (optionally by user) user information / company name (optionally by user) Monty Program Ab customer support contract id Data Not Sent Contents or names of any user database Anything that allows MariaDB to track down the user if the user doesn't explicitly permit it What will run at Monty Program's or/and the users datacenter simple CGI on Apache takes a HTTP REST PUT insert received information into a database database schema is TBD, but not complicated Analysis/Reporting/Business Process are TBD What will run on the users' machines Daemon Plugin module can be dynamically loaded, or statically compiled runs as part of the mysqld process daemon plugins have full access to server internals Start and use it's own thread will not block normal operation will yield often will hold read mutexs as short as possible Loop and delay on an interval (specified by option) probably default to be on server restart and about once a week randomly spread time to avoid too many calling in at the same moment Gather data from internal mysqld data structures Convert data into simple text format (human readable) Transmit data via HTTP REST POST to one or more given URLs ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Igor): Partitioned Key Cache for MyISAM (85)
by worklog-noreply＠askmonty.org 16 Mar '10

16 Mar '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Partitioned Key Cache for MyISAM CREATION DATE..: Sun, 14 Feb 2010, 00:10 SUPERVISOR.....: Monty IMPLEMENTOR....: COPIES TO......: Igor, Monty, Sergei CATEGORY.......: Server-Sprint TASK ID........: 85 (http://askmonty.org/worklog/?tid=85) VERSION........: Server-5.2 STATUS.........: Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 80 (hours remain) ORIG. ESTIMATE.: 80 PROGRESS NOTES: -=-=(Igor - Tue, 16 Mar 2010, 19:34)=-=- High Level Description modified. --- /tmp/wklog.85.old.22371 2010-03-16 19:34:33.000000000 +0000 +++ /tmp/wklog.85.new.22371 2010-03-16 19:34:33.000000000 +0000 @@ -15,4 +15,5 @@ the chances for threads not compete for the same key cache lock better. The idea and the original of the partitioned key cache was provided by one of -our external contributers. +our external contributers (see the attached file segmented_keycache_v2.diff with +the original patch from the contributor). -=-=(Igor - Sun, 14 Feb 2010, 00:15)=-=- Category updated. --- /tmp/wklog.85.old.9810 2010-02-13 22:15:43.000000000 +0000 +++ /tmp/wklog.85.new.9810 2010-02-13 22:15:43.000000000 +0000 @@ -1 +1 @@ -Server-BackLog +Server-Sprint -=-=(Igor - Sun, 14 Feb 2010, 00:15)=-=- Version updated. --- /tmp/wklog.85.old.9810 2010-02-13 22:15:43.000000000 +0000 +++ /tmp/wklog.85.new.9810 2010-02-13 22:15:43.000000000 +0000 @@ -1 +1 @@ -Benchmarks-3.0 +Server-5.2 -=-=(Igor - Sun, 14 Feb 2010, 00:12)=-=- New attachment: 'segmented_keycache_v2.diff' DESCRIPTION: A partitioned key cache is a collection of structures for regular MyiSAM key caches called key cache partitions. Any page from a file can be placed into a buffer of only one partition. The number of the partition is calculated from the file number and the position of the page in the file, and it's always the same for the page. The function that maps pages into partitions takes care of even distribution of pages among partitions. Partition key cache mitigate one of the major problem of simple key cache: thread contention for key cache lock (mutex). Every call of a key cache interface function must acquire this lock. So threads compete for this lock even in the case when they have acquired shared locks for the file and pages they want read from are in the key cache buffers. When working with a partitioned key cache any key cache interface function that needs only one page has to acquire the key cache lock only for the partition the page is ascribed to. This makes the chances for threads not compete for the same key cache lock better. The idea and the original of the partitioned key cache was provided by one of our external contributers (see the attached file segmented_keycache_v2.diff with the original patch from the contributor). ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Igor): Partitioned Key Cache for MyISAM (85)
by worklog-noreply＠askmonty.org 16 Mar '10

16 Mar '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Partitioned Key Cache for MyISAM CREATION DATE..: Sun, 14 Feb 2010, 00:10 SUPERVISOR.....: Monty IMPLEMENTOR....: COPIES TO......: Igor, Monty, Sergei CATEGORY.......: Server-Sprint TASK ID........: 85 (http://askmonty.org/worklog/?tid=85) VERSION........: Server-5.2 STATUS.........: Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 80 (hours remain) ORIG. ESTIMATE.: 80 PROGRESS NOTES: -=-=(Igor - Tue, 16 Mar 2010, 19:34)=-=- High Level Description modified. --- /tmp/wklog.85.old.22371 2010-03-16 19:34:33.000000000 +0000 +++ /tmp/wklog.85.new.22371 2010-03-16 19:34:33.000000000 +0000 @@ -15,4 +15,5 @@ the chances for threads not compete for the same key cache lock better. The idea and the original of the partitioned key cache was provided by one of -our external contributers. +our external contributers (see the attached file segmented_keycache_v2.diff with +the original patch from the contributor). -=-=(Igor - Sun, 14 Feb 2010, 00:15)=-=- Category updated. --- /tmp/wklog.85.old.9810 2010-02-13 22:15:43.000000000 +0000 +++ /tmp/wklog.85.new.9810 2010-02-13 22:15:43.000000000 +0000 @@ -1 +1 @@ -Server-BackLog +Server-Sprint -=-=(Igor - Sun, 14 Feb 2010, 00:15)=-=- Version updated. --- /tmp/wklog.85.old.9810 2010-02-13 22:15:43.000000000 +0000 +++ /tmp/wklog.85.new.9810 2010-02-13 22:15:43.000000000 +0000 @@ -1 +1 @@ -Benchmarks-3.0 +Server-5.2 -=-=(Igor - Sun, 14 Feb 2010, 00:12)=-=- New attachment: 'segmented_keycache_v2.diff' DESCRIPTION: A partitioned key cache is a collection of structures for regular MyiSAM key caches called key cache partitions. Any page from a file can be placed into a buffer of only one partition. The number of the partition is calculated from the file number and the position of the page in the file, and it's always the same for the page. The function that maps pages into partitions takes care of even distribution of pages among partitions. Partition key cache mitigate one of the major problem of simple key cache: thread contention for key cache lock (mutex). Every call of a key cache interface function must acquire this lock. So threads compete for this lock even in the case when they have acquired shared locks for the file and pages they want read from are in the key cache buffers. When working with a partitioned key cache any key cache interface function that needs only one page has to acquire the key cache lock only for the partition the page is ascribed to. This makes the chances for threads not compete for the same key cache lock better. The idea and the original of the partitioned key cache was provided by one of our external contributers (see the attached file segmented_keycache_v2.diff with the original patch from the contributor). ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Igor): Partitioned Key Cache for MyISAM (85)
by worklog-noreply＠askmonty.org 16 Mar '10

16 Mar '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Partitioned Key Cache for MyISAM CREATION DATE..: Sun, 14 Feb 2010, 00:10 SUPERVISOR.....: Monty IMPLEMENTOR....: COPIES TO......: Igor, Monty, Sergei CATEGORY.......: Server-Sprint TASK ID........: 85 (http://askmonty.org/worklog/?tid=85) VERSION........: Server-5.2 STATUS.........: Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 80 (hours remain) ORIG. ESTIMATE.: 80 PROGRESS NOTES: -=-=(Igor - Tue, 16 Mar 2010, 19:34)=-=- High Level Description modified. --- /tmp/wklog.85.old.22371 2010-03-16 19:34:33.000000000 +0000 +++ /tmp/wklog.85.new.22371 2010-03-16 19:34:33.000000000 +0000 @@ -15,4 +15,5 @@ the chances for threads not compete for the same key cache lock better. The idea and the original of the partitioned key cache was provided by one of -our external contributers. +our external contributers (see the attached file segmented_keycache_v2.diff with +the original patch from the contributor). -=-=(Igor - Sun, 14 Feb 2010, 00:15)=-=- Category updated. --- /tmp/wklog.85.old.9810 2010-02-13 22:15:43.000000000 +0000 +++ /tmp/wklog.85.new.9810 2010-02-13 22:15:43.000000000 +0000 @@ -1 +1 @@ -Server-BackLog +Server-Sprint -=-=(Igor - Sun, 14 Feb 2010, 00:15)=-=- Version updated. --- /tmp/wklog.85.old.9810 2010-02-13 22:15:43.000000000 +0000 +++ /tmp/wklog.85.new.9810 2010-02-13 22:15:43.000000000 +0000 @@ -1 +1 @@ -Benchmarks-3.0 +Server-5.2 -=-=(Igor - Sun, 14 Feb 2010, 00:12)=-=- New attachment: 'segmented_keycache_v2.diff' DESCRIPTION: A partitioned key cache is a collection of structures for regular MyiSAM key caches called key cache partitions. Any page from a file can be placed into a buffer of only one partition. The number of the partition is calculated from the file number and the position of the page in the file, and it's always the same for the page. The function that maps pages into partitions takes care of even distribution of pages among partitions. Partition key cache mitigate one of the major problem of simple key cache: thread contention for key cache lock (mutex). Every call of a key cache interface function must acquire this lock. So threads compete for this lock even in the case when they have acquired shared locks for the file and pages they want read from are in the key cache buffers. When working with a partitioned key cache any key cache interface function that needs only one page has to acquire the key cache lock only for the partition the page is ascribed to. This makes the chances for threads not compete for the same key cache lock better. The idea and the original of the partitioned key cache was provided by one of our external contributers (see the attached file segmented_keycache_v2.diff with the original patch from the contributor). ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0

[Maria-developers] Updated (by Igor): Unused (86)
by worklog-noreply＠askmonty.org 16 Mar '10

16 Mar '10

----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Unused CREATION DATE..: Sun, 14 Feb 2010, 00:17 SUPERVISOR.....: Monty IMPLEMENTOR....: Igor COPIES TO......: Igor, Monty, Sergei CATEGORY.......: Server-Sprint TASK ID........: 86 (http://askmonty.org/worklog/?tid=86) VERSION........: Server-5.2 STATUS.........: Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 80 (hours remain) ORIG. ESTIMATE.: 80 PROGRESS NOTES: -=-=(Igor - Tue, 16 Mar 2010, 19:30)=-=- Title modified. --- /tmp/wklog.86.old.22309 2010-03-16 19:30:04.000000000 +0000 +++ /tmp/wklog.86.new.22309 2010-03-16 19:30:04.000000000 +0000 @@ -1 +1 @@ -Partitioned Key Cache for MyISAM +Unused -=-=(Igor - Tue, 16 Mar 2010, 19:29)=-=- High Level Description modified. --- /tmp/wklog.86.old.22292 2010-03-16 19:29:37.000000000 +0000 +++ /tmp/wklog.86.new.22292 2010-03-16 19:29:37.000000000 +0000 @@ -1,19 +1 @@ -A partitioned key cache is a collection of structures for regular MyiSAM key -caches called key cache partitions. Any page from a file can be placed into a -buffer of only one partition. The number of the partition is calculated from the -file number and the position of the page in the file, and it's always the same -for the page. The function that maps pages into partitions takes care of even -distribution of pages among partitions. -Partition key cache mitigate one of the major problem of simple key cache: -thread contention for key cache lock (mutex). Every call of a key cache -interface function must acquire this lock. So threads compete for this lock even -in the case when they have acquired shared locks for the file and pages they -want read from are in the key cache buffers. When working with a partitioned key -cache any key cache interface function that needs only one page has to acquire -the key cache lock only for the partition the page is ascribed to. This makes -the chances for threads not compete for the same key cache lock better. - -The idea and the original of the partitioned key cache was provided by one of -our external contributers (see the attached file segmented_keycache_v2.diff with -the original patch from the contributor). -=-=(Igor - Sun, 14 Feb 2010, 00:19)=-=- Privacy level updated. --- /tmp/wklog.86.old.10092 2010-02-13 22:19:03.000000000 +0000 +++ /tmp/wklog.86.new.10092 2010-02-13 22:19:03.000000000 +0000 @@ -1 +1 @@ -y +n -=-=(Igor - Sun, 14 Feb 2010, 00:19)=-=- Category updated. --- /tmp/wklog.86.old.10092 2010-02-13 22:19:03.000000000 +0000 +++ /tmp/wklog.86.new.10092 2010-02-13 22:19:03.000000000 +0000 @@ -1 +1 @@ -Server-BackLog +Server-Sprint -=-=(Igor - Sun, 14 Feb 2010, 00:18)=-=- Version updated. --- /tmp/wklog.86.old.10044 2010-02-14 00:18:31.000000000 +0200 +++ /tmp/wklog.86.new.10044 2010-02-14 00:18:31.000000000 +0200 @@ -1 +1 @@ -Benchmarks-3.0 +Server-5.2 DESCRIPTION: ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)

1 0