- discuss - lists.mariadb.org

[Maria-discuss] Looking for mariadb-plugin-aws-key-management package on Ubuntu 18.04
by James Colannino 27 Aug '18

27 Aug '18

Hi everyone, I'm new to the list. Please forgive me if this is a dumb question, but I've been following this document: https://mariadb.com/kb/en/library/aws-key-management-encryption-plugin-setu… I'm using Ubuntu 18.04, and after adding the MariaDB repos and installing MariaDB, I get to the point where I need to install the mariadb-plugin-aws-key-management package and am told that this package isn't found. I see that other plugin packages exist, but not this one. I've done a ton of Googling, and the only clue I've been able to find is that an old cached package list of a mirror used to have this package, while the current package list for the same mirror doesn't. Was this package removed at some point? If so, I can't find any documentation online that says this occurred. I'm really confused and frustrated and hoping to get this plugin installed. Thanks in advance! :)

1 1

[Maria-discuss] Is disabling doublewrite safe on ZFS?
by Gionatan Danti 25 Aug '18

25 Aug '18

Hi all, as by subject: is disabling doublewrite safe on ZFS (and/or other CoW filesystems as BTRFS)? Background information: ZFS is a CoW/transactional filesystem, meaning that writes are atomic: they fully commit or are rolled backup to latest "stable" version. This lend many peoples to claim not only that disabling doublewrite is safe when InnoDB runs on top of a ZFS storage, but even that it is the *right* thing to do for increase InnoDB write performance. The reason is that when ZFS recordsize is set the same as InnoDB page/record size, no partial page write can happen. Some evidence: http://assets.en.oreilly.com/1/event/21/Optimizing%20MySQL%20Performance%20… However, I am not fully committed (pun intended!) to this idea. While I surely appreciate ZFS write atomicity, and how it *does* protect from system-wide crash (ie: powerloss), I fear that an InnoDB/MariaDB crash *can* lead to partial page writes. If, for example, the mysqld process crashes (or it is killed) when copying an internal buffer during a write() call, I can imagine the filesystem will receive wrong/partial data, which it will happily write to the main storage pool (as it know nothing of internal data consistency from InnoDB point of view). I understand that this failure scenario should be *really* rare, as the critical operation (buffer copy from mysqld to system pagecache/ARC via write()) is extremely fast compared to the real data flush to stable storage (meaning that the "vulnerable time window" is very small). However, it remain different from 100% safety. Moreover, it really backfired in the past: https://www.percona.com/blog/2015/06/17/update-on-the-innodb-double-write-b… From my understanding, disabling doublebuffer is really 100% safe only when enabling atomic writes on *a supported hardware* (https://mariadb.com/kb/en/library/atomic-write-support/) Am I missing something? Am I over-thinking it, maybe? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

5 15

[Maria-discuss] Fwd: CVE list for connectors
by Michal Schorm 21 Aug '18

21 Aug '18

Hello, On this page: https://mariadb.com/kb/en/library/security/ I can find CVEs that affect MariaDB server and releases they were fixed in. Other useful page is this one: https://mariadb.com/kb/en/library/security-vulnerabilities-in-oracle- mysql-that-did-not-exist-in-mariadb/ -- I'd like to ask you to also list CVEs applicable for connectors and versions of connectors (CONC, CONJ, ODBC) they were fixed in, since there is not direct relationship between: 1) server nad CONC 2) ODBC and CONC Server is (or atleast should be) built on top of released version of the CONC, not the latest Git content. Atleast downstreams starts to use this scheme (separate server and client library - the CONC), so they depend only on the released versions of the CONC. -- For example CVE-2018-3081 should be fixed in CONC 3.0.5, however since nor git commit, nor CONC release notes says it explicitly, I can only guess. -- Michal Schorm Associate Software Engineer Core Services - Databases Team Red Hat

1 0

[Maria-discuss] Drop user not replicating in 10.2.16/17 galera cluster with NO_AUTO_CREATE_USER in mysql_mode
by Vincent Hoffman-Kazlauskas 15 Aug '18

15 Aug '18

Hi all, not sure if this is expected or not. I am running a test cluster in preparation for upgrading from 10.0 to 10.2 and noticed that DROP user commands were not being propagated to other members of the galera cluster. The only user management changes of note I know of was the addition of NO_AUTO_CREATE_USER to sql_mode and indeed removing that from sql_mode appears to have resolved it. My question is, is that expected behavior and if so whats the modern way of removing mysql users from a mariadb galera cluster. If not is it worthy of a bug report? Thanks, Vince

1 0

Re: [Maria-discuss] [EXTERNAL] Re: Copying database files
by Reindl Harald 14 Aug '18

14 Aug '18

Am 13.08.2018 um 11:57 schrieb Ling, Andy: >>> I'm using MariaDB 10.2.13 on Windows 7. All tables are using the Aria >>> engine. >>> >>> I am trying to initialise a slave database by copying the files between >>> PCs, but when I try and use the copied files I get the error >>> >>> Table is from another system and must be zerofilled or repaired to be >>> usable on this system >>> >>> Repairing the tables fixes this, but I'd rather not have to so that. >>> >>> I have tried various things suggested to stop this, but nothing seems to >>> help. On the source server I have run aria_chk -zerofill on all the >>> tables. Before copying the tables I run FLUSH TABLES <table list> FOR >>> EXPORT, but I still get the error. >> jesus don't copy tbale files around while the server is running >> no idea why you repsond off-list > Does that mean this is not valid then... did you read and understand it > https://mariadb.com/kb/en/library/copying-tables-between-different-mariadb-… how make you sure "The server is not accessing the tables during the copy process" "The advantage of FLUSH TABLES table_name FOR EXPORT is that the table is read locked until UNLOCK TABLES is executed" is not really true because that's only valid for the running connection "Warning: If you do the above live copy, you are doing this on your own risk" should be clear in short: nobody right in his mind copies database tables hot

3 9

[Maria-discuss] New testsuite option
by Michal Schorm 13 Aug '18

13 Aug '18

Hello, I take care of MariaDB in Fedora & RHEL. We run the testsuite there. Every time, in every build, with --big-test. Time to time it happens that some of the tests fail. For example during a rebuild. For such cases, I'd use a way to tell MTR what is a unstable test treshold, which means "how many tests can fail to still count the testsuite run as a success". Most likely, I'd use it with value from 1-5. Any larger group of failing tests needs to get my attention. Anyway I still could spare myself of the unstable tests. -- (Asking before filling any JIRA feature request) 1) Is there already some way to do that? 2) Do you find such feature usefull? 3) Any ideas how to call such option? --max-test-fail is already used -- Michal Schorm Associate Software Engineer Core Services - Databases Team Red Hat

2 3

[Maria-discuss] Copying database files
by Ling, Andy 13 Aug '18

13 Aug '18

I'm using MariaDB 10.2.13 on Windows 7. All tables are using the Aria engine. I am trying to initialise a slave database by copying the files between PCs, but when I try and use the copied files I get the error Table is from another system and must be zerofilled or repaired to be usable on this system Repairing the tables fixes this, but I'd rather not have to so that. I have tried various things suggested to stop this, but nothing seems to help. On the source server I have run aria_chk -zerofill on all the tables. Before copying the tables I run FLUSH TABLES <table list> FOR EXPORT, but I still get the error. What do I need to do to make this work? Thanks for any help. Andy Ling ********************************************************************** DISCLAIMER: Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.

2 1

[Maria-discuss] Best way to fetch user’s password hash?
by Felipe Gasper 10 Aug '18

10 Aug '18

Hi all, What is the best way to fetch a user’s password hash? I’d ideally like something that works in both MySQL and MariaDB, as many versions as possible. Thank you! -Felipe Gasper Mississauga, Ontario

2 2

[Maria-discuss] Disable Stric Mode MariaDB 10.4
by Wilmer Arambula 04 Aug '18

04 Aug '18

Hi, i need disable strict mode Maria DB 10.4, Thks, Wilmer.

2 1

[Maria-discuss] MariaDB Zulip
by Ian Gilfillan 04 Aug '18

04 Aug '18

A reminder that MariaDB is trialling Zulip, which provides both Slack-like and IRC-like functionality. Zulip is an open-source tool that can also provide native integrations with various other tools, including GitHub. At the moment the MariaDB Foundation has been using it internally for most communications, and there's not been much public activity, but we'd like to invite developers and others interested in MariaDB to come try it out as well. So far the responses from those using it have been positive. Visit it at https://mariadb.zulipchat.com.

1 0