March 2014 - developers - lists.mariadb.org

[Maria-developers] MariaDB & MySQL community event 3rd of April 2014 in Santa Clara
by Michael Widenius 05 Mar '14

05 Mar '14

Hi! I am happy to announce that the MariaDB Foundation is organising a MariaDB & MySQL community event in Santa Clara on Thursday the 3rd of April. The venue is the Hilton Santa Clara hotel, a short walk from the Percona Live 2014 event. You can find more information on my blog at: http://monty-says.blogspot.fi/2014/03/mariadb-mysql-community-event-2014-in… We already got some very interesting talks and speakers, but I would like to see even more talk proposals. It's ok to propose a talk that it's also hold at Percona Live. As this event is free, I expect a totally different group of attendees, so that should be fine! When we have got a nice list of proposed talks, we will post them here so that everyone has a chance of commenting of which talks should be accepted. (Sorry, but this time we don't have time to create a proper selection committee so we have to do this a bit rough) Personally I will talk about MariaDB 10.0, which should be declared stable by then. Hope to see many MariaDB developers and users in Santa Clara! You can sign up for the event and/or dinner at: http://www.eventbrite.com/e/mariadb-mysql-community-event-2014-tickets-1080… Regards, Monty PS: Feel free to discuss the event on this email list! We want to have as many as possible participating in making this the best possible MariaDB and MySQL event.

1 0

[Maria-developers] regarding the project in gsoc 2014
by nitin goel 05 Mar '14

05 Mar '14

Sir/Ma'am, I would like to bring to your notice that i used 'mysql' to drop and create tables to understand project better but would like to know more specifications for the project 'create or replace, create if not exists, and drop if exists'. I have been working in C/C++ since 2010 and would like to learn more from you. Please also mention how to contact the mentor for the project and proceed further on project. Thanks Nitin Goel

2 1

[Maria-developers] MariaDB slave_parallel_threads and MySQL slave_parallel_workers
by Rasmus Johansson 05 Mar '14

05 Mar '14

Hi, I received a question that I wanted to share here to get some insight on. MariaDB 10.0 has a global setting named "slave_parallel_threads" and MySQL 5.7 has the same parameter named "slave_parallel_workers". Should slave_parallel_workers be an alias to slave_parallel_threads in MariaDB 10.0 to be more compatible with MySQL? BR, Rasmus -- Rasmus Johansson, VP Engineering MariaDB | t: +358 50 499 9589 | Skype: ratzpo

2 1

[Maria-developers] [GSoC] memcached priorities
by Tan Tran 04 Mar '14

04 Mar '14

Hi all, I'm looking to do my GSoC project with MariaDB, specifically the suggestion to "Port the InnoDB memcached interface to MariaDB" on the page https://mariadb.com/kb/en/google-summer-of-code-2014/ . But the project description links to a JIRA bug at https://mariadb.atlassian.net/browse/MDEV-4674 , where the author suggests that we support memcached through TCP/UDP instead, with no mention of the InnoDB plugin. I figure that the InnoDB plugin is more important, since it's a MySQL 5.6 feature, it's widespread in industry, and the lack of a memcache interface is one of only a handful X's for MariaDB on http://www.skysql.com/blogs/max-mether/mysql-56-vs-mariadb-100 . Additionally, even without TCP/UDP support, one could just code the memcache logic manually anyway, whereas the InnoDB integration is more sophisticated and feature-rich and would be a good selling point for SkySQL. So I'd like to start working on a proposal. Can any devs weigh in on which aspect of memcache is more desirable for MariaDB? If it sounds likes a good, straightforward GSoC project that nobody else has claimed yet? Thanks, Tan Tran

1 0

Re: [Maria-developers] Rev 4006: MDEV-5674 - Performance: my_hash_sort_bin is called too often
by Sergei Golubchik 04 Mar '14

04 Mar '14

Hi, Sergey! On Feb 14, Sergey Vojtovich wrote: > At lp:maria/10.0 > > ------------------------------------------------------------ > revno: 4006 > revision-id: svoj(a)mariadb.org-20140214122541-tenvcllk760deai8 > parent: svoj(a)mariadb.org-20140213071355-psk0jpsarx2u7myc > committer: Sergey Vojtovich <svoj(a)mariadb.org> > branch nick: 10.0 > timestamp: Fri 2014-02-14 16:25:41 +0400 > message: > MDEV-5674 - Performance: my_hash_sort_bin is called too often > > - reduced number of my_hash_sort_bin() calls from 4 to 2 per query. > Let MDL subsystem use pre-calculated hash value for hash > inserts and deletes. Is this necessary? One of the reasons why I didn't review this your first patch, because I believed that the second one obsoletes it. Why do you need my_hash_insert_using_hash_value() when you achieve the same effect with your calc_hash callback in the second patch? > - reduced number of memory accesses done by my_hash_sort_bin() I'd expect the compiler to handle it automatically, but feel free to change it, if it doesn't. Regards, Sergei

2 1

Re: [Maria-developers] MDEV-5674 - Performance: my_hash_sort_bin is called too often
by Sergei Golubchik 04 Mar '14

04 Mar '14

Hi, Sergey! On Feb 20, Sergey Vojtovich wrote: > At lp:maria/10.0 > > ------------------------------------------------------------ > revno: 4007 > revision-id: svoj(a)mariadb.org-20140220072533-ko14y1714ouvd2f7 > parent: svoj(a)mariadb.org-20140214122541-tenvcllk760deai8 > committer: Sergey Vojtovich <svoj(a)mariadb.org> > branch nick: 10.0 > timestamp: Thu 2014-02-20 11:25:33 +0400 > message: > MDEV-5674 - Performance: my_hash_sort_bin is called too often It's MDEV-5675, not MDEV-5674 > Reuse MDL hash value in table cache: > - MDL namespace is excluded from hash value calculation, so that > hash value can be used by table cache as is > - hash value for MDL is calculated as resulting hash value + MDL > namespace > - extended hash implementation to accept user defined hash function This looks ok. I have a couple of comments, but they are mostly a question of taste. Up to you, you can push as is too. > === modified file 'sql/mdl.cc' > --- a/sql/mdl.cc 2014-02-14 12:25:41 +0000 > +++ b/sql/mdl.cc 2014-02-20 07:25:33 +0000 > @@ -760,13 +760,22 @@ void MDL_map::init() > } > > > +my_hash_value_type mdl_hash_function(const CHARSET_INFO *cs, > + const uchar *key, size_t length) > +{ > + return *((my_hash_value_type*) (key - offsetof(MDL_key, m_ptr) + > + offsetof(MDL_key, m_hash_value))) + > + key[0]; I'd prefer to avoid pointer and offset juggling. Because you use a custom hash function anyway, you can directly pass MDL_key as your "key", then here you can use ((MDL_key*)key)->hash_value() > +} > + > /** Initialize the partition in the container with all MDL locks. */ > > === modified file 'sql/mdl.h' > --- a/sql/mdl.h 2014-02-14 12:25:41 +0000 > +++ b/sql/mdl.h 2014-02-20 07:25:33 +0000 > @@ -397,7 +396,11 @@ class MDL_key > { > return & m_namespace_to_wait_state_name[(int)mdl_namespace()]; > } > - ulong hash_value() const > + my_hash_value_type hash_value() const > + { > + return m_hash_value + m_ptr[0]; I'm not sure it's a good idea, + is not a very good hash function :) On the other hand, I don't see anything immediately wrong with it in this particular case. Ok, let it be. Anyway, could you please use mdl_namespace() instead of m_ptr[0] where possible? > @@ -405,12 +408,14 @@ class MDL_key > private: > MDL_key(const MDL_key &); /* not implemented */ > MDL_key &operator=(const MDL_key &); /* not implemented */ > + friend my_hash_value_type mdl_hash_function(const CHARSET_INFO *, > + const uchar *, size_t); You probably wouldn't need this friend, if you'd change mdl_hash_function() to use MDL_key::hash_value() Regards, Sergei

2 5

[Maria-developers] Suggestion ,a new member
by anupama vijjapu 04 Mar '14

04 Mar '14

Hello fellow developers, I joined MariaDB community today and need few suggestions/projects/bugs that i can work on. I do not have any knowledge of MariaDB source, but I will start looking into it now. I have hands on experience in C/C++/Java/Python and MySQL Database. Any suggestions/recommendation are highly appreciated.

2 1

Re: [Maria-developers] Rev 4029: MDEV-4856 SQL_ERROR_LOG shows 1146 errors which didnt appear in mysql client
by Sergei Golubchik 03 Mar '14

03 Mar '14

Hi, Holyfoot! On Jan 31, holyfoot(a)askmonty.org wrote: > revno: 4029 > revision-id: holyfoot(a)askmonty.org-20140131103303-1rx7ielo83f8iahe > parent: holyfoot(a)askmonty.org-20140124020722-dd5twtwlcc8o1xiy > committer: Alexey Botchkov <holyfoot(a)askmonty.org> > branch nick: mdev-4856 > timestamp: Fri 2014-01-31 14:33:03 +0400 > message: > MDEV-4856 SQL_ERROR_LOG shows 1146 errors which didnt appear in mysql client. > The fill_schema_table() function used to call get_table_share() for > a table name in WHERE then clear the error list. That way plugins > receive the superfluous error notification if it happens in it. Also > the problem was that error handler didn't prevent the suppressed > error message from logging anyway as the logging happens in > THD::raise_condition before the handler call. > Fixed by adding the No_table_error_handler before the call. > raise_condition() also fixed. > === modified file 'sql/sql_class.cc' > --- a/sql/sql_class.cc 2014-01-23 18:21:02 +0000 > +++ b/sql/sql_class.cc 2014-01-31 10:33:03 +0000 > @@ -1145,7 +1145,6 @@ MYSQL_ERROR* THD::raise_condition(uint s > got_warning= 1; > break; > case MYSQL_ERROR::WARN_LEVEL_ERROR: > - mysql_audit_general(this, MYSQL_AUDIT_GENERAL_ERROR, sql_errno, msg); > break; > default: > DBUG_ASSERT(FALSE); > @@ -1156,6 +1155,8 @@ MYSQL_ERROR* THD::raise_condition(uint s > > if (level == MYSQL_ERROR::WARN_LEVEL_ERROR) > { > + mysql_audit_general(this, MYSQL_AUDIT_GENERAL_ERROR, sql_errno, msg); > + This is good. > === modified file 'sql/sql_show.cc' > --- a/sql/sql_show.cc 2013-11-19 12:16:25 +0000 > +++ b/sql/sql_show.cc 2014-01-31 10:33:03 +0000 > @@ -4199,8 +4199,13 @@ static int fill_schema_table_from_frm(TH > key_length= create_table_def_key(thd, key, &table_list, 0); > hash_value= my_calc_hash(&table_def_cache, (uchar*) key, key_length); > mysql_mutex_lock(&LOCK_open); > - share= get_table_share(thd, &table_list, key, > - key_length, OPEN_VIEW, &not_used, hash_value); > + { > + No_such_table_error_handler no_such_table_handler; > + thd->push_internal_handler(&no_such_table_handler); > + share= get_table_share(thd, &table_list, key, > + key_length, OPEN_VIEW, &not_used, hash_value); > + thd->pop_internal_handler(); > + } But I don't understand that. Do you mean, old code did *not* suppress errors here? How could selects from I_S tables work without it? Regards, Sergei

2 5

[Maria-developers] New member, Need suggestion
by Neil Shah 03 Mar '14

03 Mar '14

Hello fellow developers, I joined MariaDB community today and need few suggestions/projects/bugs that i can work on. I do not have any knowledge of MariaDB source, but I will start looking into it now. I have hands on experience in C/C++/Java/Python and MySQL Database. Any suggestions/recommendation are highly appreciated. -- Thanks & Regards Neil Shah

2 3

[Maria-developers] slave_ddl_exec_mode and incompatible change in MariaDB 10.0.8
by Pavel Ivanov 03 Mar '14

03 Mar '14

Hi, I've discovered a change in MariaDB 10.0.8 that I don't quite understand motivation for and which looks really surprising to me. So I would appreciate if you could tell me what's the motivation and why you think it's appropriate to do that. The change in question is http://bazaar.launchpad.net/~maria-captains/maria/10.0/revision/3961.1.7. I see several issues with it: 1. It introduces a pretty significant variable slave_ddl_exec_mode which wasn't announced in the Release Notes. 2. The default variable value was set to IDEMPOTENT which changes MariaDB slave behavior in an incompatible way. Not everyone will want to have this variable set to IDEMPOTENT (I'd actually argue that no one should set it to IDEMPOTENT), but without any mentioning of this variable in the Release Notes people basically have the only chance to get knowledge about this change (let me stress out: _incompatible_ change) from production incidents or from accidental code inspection. 3. When slave_ddl_exec_mode is set to IDEMPOTENT every "DROP TABLE" event in master's binlog is converted into "DROP TABLE IF EXISTS" in slave's binlog, which I believe is a major no-no for replication. Binlogs on master and slave should be identical, otherwise after failover even if one would set slave_ddl_exec_mode = STRICT it will still execute "DROP TABLE IF EXISTS" because new master has that in binlogs. 4. Why this change introduces OPTION_GTID_BEGIN in the code? Why OPTION_BEGIN wasn't enough? From reading the code the only thing I understand is that with broken binlogs and sequence of events "GTID BEGIN; CREATE TABLE; CREATE TABLE" MariaDB will try to execute both CREATE TABLE statements in the same transaction without auto-committing at the end. This sounds pretty crazy to me. And given the fact that in normal situation such sequence of events on the master is not possible it seems that existence of both OPTION_BEGIN and OPTION_GTID_BEGIN only introduces confusion (MariaDB have GTID always on, right? So it should always execute GTID_BEGIN and never BEGIN without GTID, right?). So what is your word on this? Can you at least set default value for slave_ddl_exec_mode to STRICT so that slave behavior didn't change with the version upgrade? Thank you, Pavel

2 7