- developers - lists.mariadb.org

[Maria-developers] MariaDB 5.3.7 release prep
by Daniel Bartholomew 04 May '12

04 May '12

All, The packages and other files for MariaDB 5.3.7 have been uploaded to the primary mirror and we're waiting for the other mirrors to pick up the new files before announcing the release. I've created preliminary changelog and release notes pages for the release here: http://kb.askmonty.org/en/mariadb-537-release-notes http://kb.askmonty.org/en/mariadb-537-changelog From the changelog, it appears this is primarily a bug-fix release. If there are any particularly notable bugs or features of this release which I should make mention of in the release notes, let me know ASAP. Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-developers] proposed patch for handler APIs for range query information
by Zardosht Kasheff 02 May '12

02 May '12

Hello all, After talking with Colin Charles last night, I have been encouraged to send more patches for MariaDB. Here is a hopefully simple one that benefits all storage engines. Attached is a proposed patch of new handler APIs. The purpose of this patch is to give storage engines more information about impending range queries. The idea is if MySQL is about to perform a range query from a to b, then the handler is informed that a range query is about to happen. It extends functionality like handler::prepare_index_scan to other scenarios. We use it to know how much data to prefetch and prelock before doing a range query. Any storage engine can use this as a heuristic for optimizing range query performance. I would love to hear feedback -Zardosht

2 2

[Maria-developers] KB Question: Aria features ?
by Daniel Bartholomew 30 Apr '12

30 Apr '12

A question has been posted to the Knowledgebase: http://kb.askmonty.org/en/aria-features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Aria features ? When Aria Engine is a new generation MyISAM Engine , whether the new features: - parallel index creating? - merge table? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-developers] KB question: parallel index creating
by Daniel Bartholomew 30 Apr '12

30 Apr '12

A question has been posted to the Knowledgebase: http://kb.askmonty.org/en/parallel-index-creating - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - parallel index creating? Hi all can we expect the creation of parallel index creating in MyISAM engine? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

Re: [Maria-developers] Request for testing: MWL#182 SHOW EXPLAIN
by Sergei Petrunia 27 Apr '12

27 Apr '12

On Fri, Apr 27, 2012 at 01:31:08PM +0400, Elena Stepanova wrote: > Hi Sergey, > > OK, I will start working on this. > > > Before this WL, the code that produced EXPLAIN output > > - Required that optimizer produces a slightly different structures > > when EXPLAIN is running > > - Did destructive modifications to the query plan > > Does this mean that the traditional EXPLAIN (preceding a statement or > subsequent to it) is also affected? > Yes. I've changed regular EXPLAIN code so that it can be ran multiple times. That way, traditional EXPLAIN is affected. There is one known difference, currently only documented in this e-mail (will forward it): Date: Sat, 27 Aug 2011 10:14:13 +0400 From: Sergey Petrunya <psergey(a)askmonty.org> To: maria-developers(a)lists.launchpad.net Subject: [Maria-developers] MWL#182: a problem select_type column, SIMPLE vs PRIMARY > By the way, s there any standard way of naming the new EXPLAIN, as > opposed to the old EXPLAIN? (e.g. Online EXPLAIN? Asynchronous? Running? > Parallel?) > This is just to simplify further talks. We call it "SHOW EXPLAIN", following the SQL syntax. Nobody has made an explicit decision on the "official" way to name it, but it looks like this name will stick. > Regards, > /E > > > On 4/27/2012 9:13 AM, Sergei Petrunia wrote: >> Hi Elena, >> >> I need testing for MWL#182 SHOW EXPLAIN. >> >> The code is here: lp:~maria-captains/maria/5.3-show-explain2 (note the '2' at >> the end) >> >> The branch is currently based on 5.3, although will move to 5.5 soon (I suppose >> this doesn't cause any problems for testing). >> >> Currently, I can think of two things that need testing: >> >> === "Asynchronous Procedure Call" module === >> This is a module that allows one thread to schedule a call in the other thread, >> and wait until the call has been invoked. >> >> Suggested way to test: >> - run a set of queries that look at each other with "SHOW EXPLAIN FOR<thread>" >> statements. >> - have some "victim" threads which run long queries, and have "attacker" >> threads which submit a lot of "SHOW EXPLAIN FOR<victim_thread>" queries. >> >> === On-the-fly EXPLAIN printing functionality === >> Before this WL, the code that produced EXPLAIN output >> - Required that optimizer produces a slightly different structures when EXPLAIN >> is running >> - Did destructive modifications to the query plan (that is, it was not possible >> to call these functions two times to get two EXPLAIN outputs for the same >> planned query) >> >> Suggested way to test: >> - Run various complicated queries, with UNIONs, JOINs, etc. >> - While they are running, do SHOW EXPLAIN FOR command for them, expecting >> it to crash or produce nonsensical output at some point. >> If SHOW EXPLAIN crashes, the crash report will show the query it was trying >> to obtain the EXPLAIN for. >> >> My current suggestion is to use some "runner" threads to run the queries and >> use another set of threads to hit the "runner" threads with SHOW EXPLAIN >> request. >> >> When creating tests in mysql-test/t/show_explain.test, I made a framework that >> allows to stop query execution at some particular point and then wait until >> some number of SHOW EXPLAIN requests were arrived and served. >> >> This requires insertion of "probes" into the source code, though. >> >> Perhaps, we could use something like that for your testing: to have the query >> pause at some "interesting" points and wait for SHOW EXPLAIN requests to arrive >> and be served. I wasn't able to come up with any intelligent way to find >> interesting point though, so this is still just an idea. >> >> BR >> Sergei -- BR Sergei -- Sergei Petrunia, Software Developer Monty Program AB, http://askmonty.org Blog: http://s.petrunia.net/blog

1 0

Re: [Maria-developers] [Bug 988694] Re: Client software depends on server PAM plugin setup
by sergii＠pisem.net 27 Apr '12

27 Apr '12

Hi, Predrag! On Apr 27, Predrag Zecevic wrote: > @Sergei, > > is that MariaDB PAM plugin portable to MySQL? > > Regards. > > BTW, thanks for clarifications about PAM plugin usage for MySQL. I'm taking this out of percona-pam-plugin bug report, hope it's ok. Personally, I didn't try it with MySQL. But because pluggable authentication in MySQL is pretty much the same as in MariaDB (in fact, we've implemented it, and contributed to Oracle), our pam plugin should work. It might need minor cosmetic changes to compile though. Alternatively, you can simply use MariaDB :) it has everything that MySQL does, plus much faster subqueries, much faster replication, and tons of other goodies. Regards, Sergei

2 1

[Maria-developers] lp:maria -> 5.3 or 5.5?
by Sergei Golubchik 27 Apr '12

27 Apr '12

Hi, Currently lp:maria is the same as lp:maria/5.3 - our main 5.3 branch. Typically for projects on launchpad, the short url points to a trunk. In our case it's an old (not even the latest) GA branch. I suggest to move lp:maria to be lp:maria/5.5 at once. And change to lp:maria/trunk as soon as we'll have it. Objections? Regards, Sergei

2 1

Re: [Maria-developers] bsd9 buildbot host
by Kristian Nielsen 27 Apr '12

27 Apr '12

Daniel Bartholomew <dbart(a)montyprogram.com> writes: > I've installed buildbot on the bsd9 host at Timour's office and set it > up as a buildslave. > However, the builder keeps throwing an exception right at the start of > the compile step. For example build 4: > http://buildbot.askmonty.org/buildbot/builders/bsd9-64/builds/4 > > The err.html file says: "exceptions.KeyError: 'keepstamp'" and the > err.text file says: "Traceback from remote host -- Traceback > unavailable". Looks like this is this bug: http://trac.buildbot.net/ticket/1995 Apparently this happens when Buildbot master tries to download the compiler warning suppression file from the slave. The `keepstamp' argument is mandatory for such download on the version of buildslave installed on that host due to above bug (IIUC). The easiest fix is probably just to disable the download of the suppression file. I think we can live without it. I tried that, and it seems to work - compile is running now. - Kristian.

1 0

[Maria-developers] MariaDB & InnoDB native aio disabled
by jocelyn fournier 25 Apr '12

25 Apr '12

Hi, I've just figured out after installing MariaDB 5.5.23 on two server (one directly from the x64 binary, and the other using the debian packing) that innodb_use_native_aio is OFF on the two servers. Before upgrading to MariaDB, I was using percona 5.5.21-rel25.1-234.squeeze, and innodb_use_native_aio was properly used. There's nothing wrong reported in the MySQL log. The log with percona 5.5.21 : 120425 3:55:46 InnoDB: The InnoDB memory heap is disabled 120425 3:55:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins 120425 3:55:46 InnoDB: Compressed tables use zlib 1.2.3 120425 3:55:46 InnoDB: Using Linux native AIO 120425 3:55:46 InnoDB: Initializing buffer pool, size = 9.0G 120425 3:55:47 InnoDB: Completed initialization of buffer pool 120425 3:55:47 InnoDB: highest supported file format is Barracuda. 120425 3:55:50 InnoDB: Waiting for the background threads to start 120425 3:55:51 Percona XtraDB (http://www.percona.com) 1.1.8-rel25.1 started; log sequence number 33812567651 The log with mariadb 5.5.23 : 120425 3:41:04 InnoDB: The InnoDB memory heap is disabled 120425 3:41:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins 120425 3:41:04 InnoDB: Compressed tables use zlib 1.2.3.4 120425 3:41:04 InnoDB: Initializing buffer pool, size = 9.0G 120425 3:41:04 InnoDB: Completed initialization of buffer pool 120425 3:41:04 InnoDB: highest supported file format is Barracuda. 120425 3:41:08 InnoDB: Waiting for the background threads to start 120425 3:41:09 Percona XtraDB (http://www.percona.com) 1.1.8-24.1 started; log sequence number 33812411088 (no more line saying Linux native AIO is used) Am I missing something ? Thanks and regards, Jocelyn Fournier -- This message was sent from Launchpad by jocelyn fournier (https://launchpad.net/~joce) to each member of the Maria Discuss team using the "Contact this team" link on the Maria Discuss team page (https://launchpad.net/~maria-discuss) For more information see https://help.launchpad.net/YourAccount/ContactingPeople

1 0

Re: [Maria-developers] [Commits] Rev 3365: Dependency of tests from ulong size removed. in file:///home/bell/maria/bzr/work-maria-5.5-MDEV-219-1/
by Sergei Golubchik 19 Apr '12

19 Apr '12

Hi, Sanja! On Apr 19, sanja(a)montyprogram.com wrote: > At file:///home/bell/maria/bzr/work-maria-5.5-MDEV-219-1/ > > ------------------------------------------------------------ > revno: 3365 > revision-id: sanja(a)montyprogram.com-20120419130044-inzqd6nnksyhcpa1 > parent: sergii(a)pisem.net-20120405135727-1kxtscd76rq6xw5o > committer: sanja(a)montyprogram.com > branch nick: work-maria-5.5-MDEV-219-1 > timestamp: Thu 2012-04-19 16:00:44 +0300 > message: > Dependency of tests from ulong size removed. Looks ok to me. But, please, don't push it directly to 5.5, run it in Buildbot on a stage tree first. If that'll show up all green - please push into 5.5. Regards, Sergei

1 0