January 2017 - discuss - lists.mariadb.org

[Maria-discuss] 10.1.21 - tests: main.compound w5 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

main.compound w5 [ fail ] Test ended at 2017-01-21 16:21:47 CURRENT_TEST: main.compound --- /usr/share/mysql-test/r/compound.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/compound.reject 2017-01-21 16:21:47.413144793 +0100 @@ -28,13 +28,16 @@ include/show_binlog_events.inc Log_name Pos Event_type Server_id End_log_pos Info master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (4) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (5) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (6) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT DROP TABLE t1| CREATE DATABASE mysqltest1| @@ -144,12 +147,17 @@ execute stmt using @a, @b, @c| include/show_binlog_events.inc Log_name Pos Event_type Server_id End_log_pos Info -master-bin.000001 # Gtid # # GTID #-#-# -master-bin.000001 # Query # # use `test`; SELECT `test`.`fn`(9) -master-bin.000001 # Gtid # # GTID #-#-# -master-bin.000001 # Query # # use `test`; SELECT `test`.`fn`(1) master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; insert t1 values( NAME_CONST('a',4)+3) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F +master-bin.000001 # Query # # COMMIT +master-bin.000001 # Gtid # # BEGIN GTID #-#-# +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F +master-bin.000001 # Query # # COMMIT +master-bin.000001 # Gtid # # BEGIN GTID #-#-# +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT drop function fn| drop table t1| mysqltest: Result length mismatch

1 0

[Maria-discuss] 10.1.21 - tests: main.commit_1innodb 'xtradb' w6 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

main.commit_1innodb 'xtradb' w6 [ fail ] Test ended at 2017-01-21 16:21:39 CURRENT_TEST: main.commit_1innodb --- /usr/share/mysql-test/r/commit_1innodb.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/commit_1innodb.reject 2017-01-21 16:21:39.268245094 +0100 @@ -710,12 +710,12 @@ # drop temporary table t2; call p_verify_status_increment(1, 0, 1, 0); -SUCCESS - +ERROR +Expected commit increment: 1 actual: 0 commit; call p_verify_status_increment(1, 0, 1, 0); -SUCCESS - +ERROR +Expected commit increment: 1 actual: 0 # 26. Verify that SET AUTOCOMMIT issues an implicit commit # insert t1 set a=3; @@ -831,8 +831,8 @@ Note 1050 Table 't2' already exists # Sic: first commits the statement, and then the transaction. call p_verify_status_increment(0, 0, 0, 0); -SUCCESS - +ERROR +Expected commit increment: 0 actual: 2 create table t3 select a from t2; call p_verify_status_increment(2, 0, 4, 4); SUCCESS mysqltest: Result length mismatch

1 0

[Maria-discuss] what about cleanly deprecation of config options
by Reindl Harald 20 Jan '17

20 Jan '17

what about spit some warnings in 10.0.x releases instead after update to 10.1.x service not starting and you can look what confdig options needs to be removed 2017-01-20 16:34:36 140555676232000 [ERROR] /usr/libexec/mysqld: unknown option '--skip-federated' 2017-01-20 16:34:36 140555676232000 [ERROR] Aborting

3 9

[Maria-discuss] -DWITH_INNODB_DISALLOW_WRITES=OFF and still generated files
by Reindl Harald 20 Jan '17

20 Jan '17

10.1.21 - first try build 10.1.x -DWITH_INNODB_DISALLOW_WRITES=OFF and the stuff below is still built - why? Fehler beim Bauen des RPM: Installierte (aber nicht gepackte) Datei(en) gefunden: /usr/bin/wsrep_sst_common /usr/bin/wsrep_sst_mysqldump /usr/bin/wsrep_sst_rsync /usr/bin/wsrep_sst_xtrabackup /usr/bin/wsrep_sst_xtrabackup-v2 /usr/share/mysql/wsrep.cnf /usr/share/mysql/wsrep_notify

2 2

[Maria-discuss] sanity check: mysql_upgrade MariaDB 5.5 straight to 10.1
by mike bayer 19 Jan '17

19 Jan '17

Hi all - I believe I know the answer to this question, however hoping someone can confirm all the assumptions (looks like there are three) are correct. Basically if one installs mariadb-10.1 on top of a data directory that's currently 5.5, and we run mysql_upgrade, is it as good/compatible/safe as if we had upgraded first to 10.0 in the interim? Per mariadb's documentation: https://mariadb.com/kb/en/mariadb/upgrading-from-mariadb-55-to-mariadb-100/ "There are no changes in table or index formats between MariaDB 5.5 and MariaDB 10.0" https://mariadb.com/kb/en/mariadb/upgrading-from-mariadb-100-to-101/, "There are no changes in table or index formats between MariaDB 10.0 and MariaDB 10.1" So assumption 1, transitively we can conclude there are no changes in table or index formats between 5.5 and 10.1. Next, mysql_upgrade seems like it alters some tables in the mysql database, and runs mysqlcheck --check-upgrade --auto-repair, which itself is mainly running CHECK TABLE. assumption 2 is then: the table changes in mysql_upgrade work against a 5.5 database going straight to 10.1. This would mean that if there were some tables/column changes in 5.5->10.0, and some more in 10.0->10.1, the mysql_upgrade command encapsulates both sets of changes as shipped in 10.1. It looks like this step comes from the .sql files in scripts/ by way of concatenating them into the "comp_sql" tool. Doing a diff of these scripts between 10.0.28 and 10.1.18 seems like only mysql_system_tables_fix.sql has the important bits (we don't use the performance schema stuff) and it looks like it only adds ALTER statements for more columns, the new columns from the 10.0 script are maintained. Not to mention it documents in a very open-ended way "This part converts any old privilege tables to privilege tables suitable for current version of MySQL". assumption 3 is, the Mariadb 10.1 engine running CHECK TABLE against a 5.5 database is fully compatible. The schema changes seem to be straightforward and as CHECK TABLE seems to regard the table and index formats which in assumption 1 have not changed, this should be totally fine as well. Note that I'm being kind of vague about what mysql_upgrade and mysqlcheck do, as I've only read the public documentation, browsed the source code a bit and am hoping this is all there is to it. There are a few blog posts on the web that illustrate a 5.5->10.1 direct upgrade, but these are not "official". Thanks for any guidance people can offer here!

1 0

[Maria-discuss] MariaDB 10.1.21 and other releases now available
by Daniel Bartholomew 18 Jan '17

18 Jan '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.21, MariaDB 10.0.29, MariaDB Galera Cluster 10.0.29, MariaDB Connector/J 1.5.7, MariaDB Connector/C 2.3.2, and MariaDB Connector/C 3.0.1 Beta. Apart from Connector/C 3.0.1 Beta, these are all stable (GA) releases. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.21 - Release Notes: https://mariadb.com/kb/en/mdb-10121-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10121-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.21 About MariaDB 10.1: - https://mariadb.com/kb/en/what-is-mariadb-101/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB 10.0.29 - Release Notes: https://mariadb.com/kb/en/mdb-10029-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10029-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.0.29 About MariaDB 10.0: - https://mariadb.com/kb/en/what-is-mariadb-100/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Galera Cluster 10.0.29 - Release Notes: https://mariadb.com/kb/en/mgc-10029-rn/ - Changelog: https://mariadb.com/kb/en/mgc-10029-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/10.0.29 About MariaDB Galera Cluster: - https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/J 1.5.7 - Release Notes: https://mariadb.com/kb/en/mcj-157-rn/ - Changelog: https://mariadb.com/kb/en/mcj-157-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.5.7/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ MariaDB Connector/C 2.3.2 - Release Notes: https://mariadb.com/kb/en/mcc-232-rn/ - Changelog: https://mariadb.com/kb/en/mcc-232-cl/ - Downloads: https://downloads.mariadb.org/connector-c/2.3.2/ About MariaDB Connector/C: - https://mariadb.com/kb/en/about-mariadb-connector-c/ MariaDB Connector/C 3.0.1 Beta - Release Notes: https://mariadb.com/kb/en/mcc-301-rn/ - Changelog: https://mariadb.com/kb/en/mcc-301-cl/ - Downloads: https://downloads.mariadb.org/connector-c/3.0.1/ About MariaDB Connector/C: - https://mariadb.com/kb/en/about-mariadb-connector-c/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "feedback=ON" to your my.cnf or my.ini file! See http://mariadb.com/kb/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: - http://mariadb.org/jira - - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - If you would like to contribute to the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] Handlersocket and stale data
by Sales 15 Jan '17

15 Jan '17

Is it still the case that Handlersocket may return stale data when the underlying structure is updated? Since there is still no memcached plugin in Mariadb, hoping stale data is not an issue. Steve

1 0

[Maria-discuss] ON update timestamp replication
by Artem Kuchin 14 Jan '17

14 Jan '17

Hello! Both master and slave run: Server version: 10.1.14-MariaDB FreeBSD Ports Replication is based on mixed format. Slave is used for backups without locking and going off line. I have a script that runs once a day and checksums all tables, so all tables are 100% in match (it wait for sync, locks and checksums). One table is very often out of sync. ON MASTER: show create table Message193; CREATE TABLE `Message193` ( `Message_ID` int(11) NOT NULL AUTO_INCREMENT, `User_ID` int(11) NOT NULL, `Subdivision_ID` int(11) NOT NULL, `Sub_Class_ID` int(11) NOT NULL, `Priority` int(11) NOT NULL DEFAULT '0', `Keyword` char(255) NOT NULL, `ncTitle` varchar(255) DEFAULT NULL, `ncKeywords` varchar(255) DEFAULT NULL, `ncDescription` text, `ncSMO_Title` varchar(255) DEFAULT NULL, `ncSMO_Description` text, `ncSMO_Image` char(255) DEFAULT NULL, `Checked` tinyint(4) NOT NULL DEFAULT '1', `IP` char(15) DEFAULT NULL, `UserAgent` char(255) DEFAULT NULL, `Parent_Message_ID` int(11) NOT NULL DEFAULT '0', `Created` datetime NOT NULL, `LastUpdated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `LastUser_ID` int(11) NOT NULL, `LastIP` char(15) DEFAULT NULL, `LastUserAgent` char(255) DEFAULT NULL, `Type` char(255) DEFAULT NULL, `Title` char(255) DEFAULT NULL, `Background` char(255) DEFAULT NULL, `Link` char(255) DEFAULT NULL, PRIMARY KEY (`Message_ID`), UNIQUE KEY `Sub_Class_ID` (`Sub_Class_ID`,`Message_ID`,`Keyword`), KEY `User_ID` (`User_ID`), KEY `LastUser_ID` (`LastUser_ID`), KEY `Subdivision_ID` (`Subdivision_ID`), KEY `Parent_Message_ID` (`Parent_Message_ID`), KEY `Priority` (`Priority`,`LastUpdated`), KEY `Checked` (`Checked`), KEY `Created` (`Created`) ) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8 | ON SLAVE CREATE TABLE `Message193` ( `Message_ID` int(11) NOT NULL AUTO_INCREMENT, `User_ID` int(11) NOT NULL, `Subdivision_ID` int(11) NOT NULL, `Sub_Class_ID` int(11) NOT NULL, `Priority` int(11) NOT NULL DEFAULT '0', `Keyword` char(255) NOT NULL, `ncTitle` varchar(255) DEFAULT NULL, `ncKeywords` varchar(255) DEFAULT NULL, `ncDescription` text, `ncSMO_Title` varchar(255) DEFAULT NULL, `ncSMO_Description` text, `ncSMO_Image` char(255) DEFAULT NULL, `Checked` tinyint(4) NOT NULL DEFAULT '1', `IP` char(15) DEFAULT NULL, `UserAgent` char(255) DEFAULT NULL, `Parent_Message_ID` int(11) NOT NULL DEFAULT '0', `Created` datetime NOT NULL, `LastUpdated` timestamp NOT NULL, `LastUser_ID` int(11) NOT NULL, `LastIP` char(15) DEFAULT NULL, `LastUserAgent` char(255) DEFAULT NULL, `Type` char(255) DEFAULT NULL, `Title` char(255) DEFAULT NULL, `Background` char(255) DEFAULT NULL, `Link` char(255) DEFAULT NULL, PRIMARY KEY (`Message_ID`), UNIQUE KEY `Sub_Class_ID` (`Sub_Class_ID`,`Message_ID`,`Keyword`), KEY `User_ID` (`User_ID`), KEY `LastUser_ID` (`LastUser_ID`), KEY `Subdivision_ID` (`Subdivision_ID`), KEY `Parent_Message_ID` (`Parent_Message_ID`), KEY `Priority` (`Priority`,`LastUpdated`), KEY `Checked` (`Checked`), KEY `Created` (`Created`) ) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8 | Notice that `LastUpdated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, on slave becomes `LastUpdated` timestamp NOT NULL, This is already bad enough because if master is lost then slave will not be the same as master, trigger are not restored. Now check records: MASTER MariaDB [anapolisdom_ru]> select * from Message193 limit 1\G *************************** 1. row *************************** Created: 2016-11-25 13:25:09 LastUpdated: 2016-11-25 13:25:09 MariaDB [anapolisdom_ru]> select * from Message193 limit 1\G Created: 2016-11-25 13:25:09 LastUpdated: 0000-00-00 00:00:00 As you see lastupdated field is not replicated at all. Two questions, problems: 1) How to replicate default value and on update part for this field? 2) How to make it replicate the timestamp value? Artem

3 5

[Maria-discuss] Enabling Github integration with JIRA
by jocelyn fournier 13 Jan '17

13 Jan '17

Hi all, Currently there's no way when a JIRA ticket is closed to have a direct access to the associated commits in Github. GitHub integration with JIRA is available, and quite easy to configure, so it would be great to have it enabled on MariaDB Server. Do you think it's possible? Thanks! -- Jocelyn Fournier Founder M : +33 6 51 21 54 10 https://www.softizy.com Softizy - At your side to Optimize your PHP / MySQL applications

3 2

[Maria-discuss] Issue with MariaDB-server-5.5.54-1.el6.x86_64
by Clint Dilks 05 Jan '17

05 Jan '17

Hi, Today I have updated a CentOS 6.8 system that has MariaDB-server installed from http://yum.mariadb.org/5.5/centos6-amd64 and found that I had an SELinux issue when I tried to restart the service. Using the information at https://wiki.centos.org/HowTos/SELinux I have created a local policy that seems to fix things module marialocal 1.0; require { type mysqld_safe_t; class capability { setuid setgid }; } #============= mysqld_safe_t ============== allow mysqld_safe_t self:capability setgid; allow mysqld_safe_t self:capability setuid; This seems to fix things for me, but I thought I had better see if others are experiencing the same problem ? It may be useful to know that the particular rpms are MariaDB-server-5.5.54-1.el6.x86_64 and selinux-policy-3.7.19-292.el6_8.2.noarch. If it is a bigger issue than just myself, should I report this somewhere else to see if we can get a fix added to the next MariaDB-server rpm ? Thanks

2 2