- discuss - lists.mariadb.org

Re: [Maria-discuss] Bundle more relevant cnf files in MariaDB package
by Haidong Ji 12 Mar '11

12 Mar '11

cool, Kurt von Finck, I will do it. I couldn't find a good enough translation in English of the “遣将不如激将” phrase, but I like your message. I will dig around the source code base in Launchpad, and get this damn thing started. I bet those config files are old relic from 10 years ago, or even more. 可八方，好，“遣将不如激将”，我会按你的建议去做！ On Fri, Mar 11, 2011 at 5:23 PM, Kurt von Finck <kurt(a)montyprogram.com> wrote: > On Fri, Mar 11, 2011 at 2:56 PM, Haidong Ji <haidong.ji(a)gmail.com> wrote: >> Hi, >> >> I alluded to this in IRC maybe a couple of weeks back. That is, it is >> really to have intelligent default for MariaDB servers. >> >> In particular, the bundled sample my.cnf files, under >> /usr/local/mysql/support-files, such as my-small.cnf, my-medium.cnf, >> my-large.cnf, and my-huge.cnf, are laughable in today's world. In the >> my-huge.cnf, it talks about memory between 1G and 2G as huge. It will >> be good that MariaDB can bundle a different set, like what has been >> mentioned here: >> >> http://datastrangler.com/windpipe/2011/02/24/custom-mysql-config-files-to-e… >> >> I think the sample cnf files in the above blog post is a good starting point. >> >> Thanks, >> Haidong "Alex" Ji >> >> PS: I modified http://kb.askmonty.org/v/installing-mariadb-binary-tarballs >> with the addition of modifying $PATH so a casual user will be able to >> use various MariaDB clients after the install. > > Not to sound snarky, but MariaDB is an open project. I would encourage > you to create sample my.cnf files, and submit them with bzr for review > and approval by a maria-captain. > > The real beauty of an open project is the ability to DIY for the > improvements and changes you think are important. Just Do It. :) > > -- > ./k > > Kurt von Finck > Chief Community And Communications Officer > Monty Program > http://montyprogram.com >

1 0

[Maria-discuss] MariaDB High Availability Solutions
by Daniel Bartholomew 03 Mar '11

03 Mar '11

A new question on the KB: http://kb.askmonty.org/v/mariadb-high-availability-solutions -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org

1 0

[Maria-discuss] Manning a MariaDB booth in Santa Clara April 12-13 2011
by Colin Charles 01 Mar '11

01 Mar '11

Hi! This is a call for volunteers. MariaDB is planning to have a booth at the O'Reilly MySQL Conference & Expo 2011 happening April 11-14 2011 in Santa Clara, California, USA. Volunteers are needed to man the booth April 12-13 2011. Are you local to the area? Do you dig MariaDB? This is your chance to come join a few of us and help spread the good word More information at: http://en.oreilly.com/mysql2011 Please respond to this email (either on list, or privately) if you are available and local to the area Thanks cheers, -c -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/

1 0

[Maria-discuss] Installing MariaDB using MySQL Workbench on Windows
by Jake Drew 21 Feb '11

21 Feb '11

Hello everyone, I am trying to install MariaDB locally on a Windows XP desktop machine for testing purposes. We have a server coming (eventually), but I would like to get started in the meantime. There does not seem to be much information on installing and configuring MariaDB on Windows for use with the MySQL Workbench. *Here are the steps I have taken so far:* *Installed MariaDB on windows:* 1. Downloaded and ran MariaDB-5.2.4-win32-alt.exe *Created MariaDB my.ini configuration file* 2. Copied C:\Program Files\MariaDB 5.2.4\my-large.ini 3. Pasted to C:\Program Files\MariaDB 5.2.4\*my.ini* with no modifications ** *Created a Windows Service for MariaDB named MySQL and start that service on Windows:* 4. Start > Run > cmd.exe (open a command prompt) 5. cd C:\Program Files\MariaDB 5.2.4\bin 6. mysqld.exe --install MariaDB --defaults-file="C:\Program Files\MariaDB 5.2.4\my.ini" (got message "service was installed successfully", also see service listed in the "Services" window. 7. net start MariaDB (Service shows as started in "Services" window) *Installed MySQL Workbench:* 8. Downloaded and ran mysql-workbench-gpl-5.2.31a-win32.msi *Set up MariaDB Server on MySQL Workbench:* 9. Start MySQL Workbench and select "Create New Server Instance" 10. Made sure "Path to configuration file" under "Windows Management" pointed to: C:\Program Files\MariaDB 5.2.4\my.ini 11. Named the new server instance "MariaDB" 12. Double clicked the new server instance "MariaDB" after it was created. *Got what appear to be success messages:* 2011-02-17 15:23:47 - Workbench will use cmd shell commands to start/stop this instance 2011-02-17 15:23:47 - Status check of service 'MariaDB' returned running 2011-02-17 15:23:48 - Server is running 2011-02-17 15:34:10 - Status check of service 'MariaDB' returned running *Questions:* 1. Is there anything else I should do to configure MariaDB for use under Windows? 2. Almost all tabs under the "Configuration" section are blank in MySQL Workbench for the ner server instance MariaDB. This was not the case when I was running MySQL 5.1.53 on Windows. Is this normal? If not, can it be resolved? Thanks! Jake Drew

5 5

[Maria-discuss] Error on starting MariaDB
by Joshua Partogi 18 Feb '11

18 Feb '11

Hi all, I am getting this error when starting mariadb-5.2.4: [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables I compiled mariadb from source. Can anybody give me a shed of light on what I need to do to resolve the problem? Thanks heaps. -- http://twitter.com/jpartogi

2 1

[Maria-discuss] Question about FORCE INDEX and records_in_range
by MARK CALLAGHAN 27 Jan '11

27 Jan '11

We suspect that our servers do too much extra disk IO in ha_innobase::records_in_range to determine selectivity for indexes that don't get used in a query. For example when there are multiple indexes that might be used, I assume that the MySQL optimizer calls records_in_range for each and I know that InnoDB does two index lookups per call to find the leaf blocks for the start and stop predicates of the index scan. For the index that is used on the query any disk IO done in records_in_range isn't wasted. We can think of it as prefetch. But for the other indexes that disk IO is likely to be wasted. I rarely touch or even read optimizer code in MySQL. How difficult would it be to have an option to either not call records_in_range when a hint is used (such as FORCE INDEX or REALLY FORCE INDEX)? The alternative is to figure out in records_in_range when the special hint has been used for an index other than the one for which records_in_range was called and return a large value without doing index lookups for all but the hinted index. -- Mark Callaghan mdcallag(a)gmail.com

3 4

[Maria-discuss] Glibc 2.3 support in MariaDB builds ?
by Jocelyn Fournier 19 Dec '10

19 Dec '10

Hi, I'm trying to push my company to adopt MariaDB 5.2. Unfortunately, the currently available binaries (at least for the x86-64 version) requires a glibc 2.4, where we have only a 2.3 version (debian etch) installed on our server. MySQL 5.5 standard binaries, as well as Percona's one perfectly support glibc 2.3, so is there any plan to provide glibc 2.3 compatible binaries for MariaDB ? Thanks and regards, Jocelyn Fournier

2 2

[Maria-discuss] SphinxSE missing plug.in
by Brian Evans 17 Dec '10

17 Dec '10

MariaDB 5.2.4 tarball is missing the SphinxSE plug.in file in storage/sphinx. I'm not sure if this was intentional or not, so I thought I might point it out.

2 1

Re: [Maria-discuss] Per-db binlogging
by Weldon Whipple 14 Dec '10

14 Dec '10

Sergei, Thank you very much for your reply! A later post by Henrik Ingo seems to say that I should cc maria-discuss(a)lists.launchpad.net. I'll try it and see if it bounces--I THINK I'm registered with launchpad.net :-) Let me know if sending to both lists annoys anyone, and I will quit the cc :-) See my responses below On Wed, Sep 15, 2010 at 1:53 PM, Sergei Golubchik <serg(a)askmonty.org> wrote: > Hi, Weldon! > > On Sep 13, Weldon Whipple wrote: <snip/> >> Is it plausible to identify all places where a binlog addition might >> occur? In those places, if the singleton USER_BIN_LOG_MRG exists, ask >> it if the current DB is being binlogged. If so, send the request to >> the DB_BIN_LOG instance. > > By "addition" you mean when an event is written to binlog? Yes! (exactly)--any event relating to that database that is written to binlog. (Hmm ... I wonder if there might ever be more "global" events that should be written ... Maybe we don't care about them??). Also, since these databases are "tied" to a user on a box, we probably don't care about renaming a DB ... > See where mysql_bin_log.write is called. Excellent information! (I was hoping it might be that easy ???). If I succeed in making a DB_BINLOG class derive from MYSQL_BIN_LOG (with an instance of DB_BINLOG for each database that is currently binlogging), I could--in theory, at least--just call something like db_binlog->write () at those places. > >> Questions I Have. >> ---------------- >> >> 1. I notice that binlog is in the list of engines and plugins >> (displayed by SHOW ...). The bottom of log.cc has >> "mysql_declare_plugin(binlog)". Do I need one for db_plugin? >> (probably not?) > > depends. > binlog needs to be declated a plugin, to be able to pretent being a > storage engine, to be able to force two phase commit (2PC). > > 2PC is used to commit or rollback a transaction atomically in more than > one engine. And MySQL only uses 2PC when a transaction spans more than > one engine. But we want a transaction to be committed in the engine and > written to a binlog - and it should be done atomically too. So, binlog > pretends to be an engine, pretends to participate in a transaction, > which forces MySQL to use 2PC which can guarantee that a transaction > is either committed and written to a binlog - or not committed and not > written. Reliably, even if MySQL crashes in the middle. > > So, if you don't use innodb, or don't use > innodb_flush_log_at_trx_commit=1 or don't use sync_binlog=1 > you probably don't need to support 2PC as your setup is not crash proof > anyway. > > If you care about innodb<->binlog consistency in the presence of > crashes, you should support 2PC in your binlog, as explained above. We DO have a small percentage of innodb databases. If 2PC commits (rolls back, etc.) atomically to more than one engine, does that mean TWO (only)? ... or could it happen for three (specifically, innodb, MYSQL_BIN_LOG's binlog, and DB_BIN_LOG's binlog)? The two kinds of binlog files would have the same format (except that one is for only one database). Are they considered two storage engines/plugins? (I notice that the "mysql_declare_plugin(binlog)" declaration is at the bottom of log.cc. Most of the other storage engines' corresponding declarations are in files in the storage subdirectories. If I were to need a "mysql_declare_plugin(db_binlog)" declaration, could it also go at the bottom of log.cc? ... Or (since a DB_BINLOG is AKO [a kind of] MYSQL_BIN_LOG [in the OO sense]), are MYSQL_BIN_LOGs and DB_BINLOGs both kinds of binlog plugins ...? >> 2. I've diagrammed the binary log event taxonomy--the 24 classes that >> inherit from Log_event (in log_event.cc/h). That was my main >> motivation for wanting to inherit from MYSQL_BIN_LOG. > > Was that a question? :) No. Just justification for my desire to simplify by having DB_BINLOG extend the MYSQL_BIN_LOG class. (I realize that I MIGHT have to add "virtual" in front of a method or two--possibly. Hopefully I would need to make no--or minimal-- changes to MYSQL_BIN_LOG.) >> 3. On the other hand, I wonder if inheriting from MYSQL_BIN_LOG might >> be overkill for "master only" binlogging--without the >> slave/replication part of it. > > No, I think inheriting from MYSQL_BIN_LOG is correct. > At least it's much easier to build on existing binlogging than to > implement everything from scratch. Amen!! >> 4. What version should I be working on? (We're currently running >> 5.1.47.) What should I check out of bzr/launchpad? (Is that still >> what we're doing with the changes in ownership?) > > What version you plan to use? > If it'll be 5.1 - you have to work in 5.1, use lp:mysql-server/5.1 > branch: > > bzr branch lp:mysql-server/5.1 We TRY to keep as current as possible (at the company). At some point, we'll need to move to the next major release--whatever it ends up being. (Then there is also the unknown [to me] of MySQL vs. MariaDB ... :-) We'll use bzr branch lp:mysql-server/5.1 > >> 5. I see that THD is involved in binlogging. (Several THD methods are >> defined in log.cc.) Are there any caveats here? > > There is a binlog cache (or buffer) in THD that stores binlog events for > the current transaction. They all are written to disk together, when a > transaction is committed. You need to decide what you want to do when > the current database is changed in the middle of a transaction - what > binlog the transaction should be written to. By "the current database is changed", I imagine you refer to the "USE 'database';" command. That's a good question. I THINK we have decided to ignore (for the present, at least), queries (and also transactions?) that involve multiple databases. Because we are doing per-DB binlogging, if multiple databases are involved, we (almost) consider it an anomaly at our ISP ... (I'm thinking that we might need to consider THD's binlog cache only for transactions that involve innodb and no more than one database ...) >> 6. What files should I use? A new h/cc pair? ... or just add to the >> hierarchy in log.h/cc? > > As you like. > New pair of files is cleaner. But it may require you to move some > declarations from log.cc to a header file, or to make some static > functions extern. All my prototypes have just expanded what is in log.cc and log.h. (I came VERY close to creating db_binlog.cc/h, however, which I would have done in some of my past--non-MySQL--projects). However, noticing most of the logging hierarchy in the single log.cc/h pair, I decided the implementors must have done it for a reason, and have decided to follow suit--for now, at least. > >> What I've Implemented So Far (about 13 Prototypes). >> -------------------------------------------------- >> >> (PRELIMINARY NOTE:) >> >> Our initial plan was to call it "Per-User Binlogging". The user here >> is a cPanel [control panel] user. cPanel's database naming convention >> is to have all of a user's database names start with the username, >> followed by an underscore, followed by a distinctive database >> name. Thus all the commands above start with >> >> <verb> USER ... >> >> Originally most of them could end either "DATABASE <db>" or "USER >> <user>" (with user meaning cPanel user). Thus, in the original plan >> the first command above was: >> >> START USER BINLOG FOR (USER <user> | DATABASE <db>) >> >> We have realized that per-database binlogging is all we really need. >> We imagine that others in our situation might want something similar. >> Since not everyone uses cPanel, we should forget per[cPanel]-user >> binlogging, focusing on per-database binlogging. > > If every user is a different MySQL account - that it a different row in > the mysql.user table - than per-user binlogging is much cleaner and > better defined concept. > > A statement can affect more than one database (say, UPDATE db1.t1, > db2.t2 SET ...), the current database may be changed in the middle of > transaction, and so on. On the other hand, any statement or a > transaction is always executed in the context of as single user - you > cannot change user in the middle of transaction. (*) > > (*) changing security context only affect privileges, but not the > destination binlog. Actually (and this is because of the way cPanel does things--I have been "bitten" by this many times!!), each database has a (different) corresponding user in the mysql.user table (!!!). So (for example), if a user signs up with our ISP with a user name of elvispre every one of his (perhaps hundreds/thousands of) databases will have names something like: elvispre_friends elvispre_earlyyears elvispre_hitsongs . . . And (here's the surprising part)--each one of those databases will have a MATCHING ROW IN mysql.user!! So, for us to migrate our customer elvispre to another physical server, we DO (ultimately) need to binlog all of the databases/users that match/are like 'elvispre\_%'; . In some of my earlier prototypes, the START/FLUSH-LOCK/SHOW/UNLOCK/STOP commands have allowed for "like" clauses at the end. Maybe I need to go that route? ALL of my prototypes have had binlogging PER DATABASE. I wonder how difficult/feasible/desirable/useful it would be to create separate binlog files for databases (or users) whose name matches a "like" clause. ... Probably more important: Would this feature be of general interest to the MySQL user community at large? (... and, if so, should it be database- or user- or database_pattern- or user_pattern-based). (My initial idea is that per [single] database/user might be easiest to define/implement??) > > Regards, > Sergei Thanks again for your reply!! Weldon

2 4

[Maria-discuss] Using MariaDB in production?
by Colin Charles 09 Dec '10

09 Dec '10

Hi! In February 2010, we released MariaDB 5.1. In November 2010, we released MariaDB 5.2. In a span of those months, we've seen a 4x increase in downloads of MariaDB. I've heard many stories of people running it on their blog, and there are people running it on single server instances. I myself run it on about six servers of mine in production... And Daniel will attest to running all the Monty Program infrastructure on MariaDB :) I'm curious to know where MariaDB is going. Where its getting installed. Are only software developers playing with it, or is it getting into production environments? Please don't hesitate to discuss it here on the maria-discuss mailing list so we can all get a better idea of where MariaDB is being used. If its being used in "secretive" environments, don't hesitate to drop me a private email Thanks! cheers, -c p/s: If you're able to, don't hesitate to display the badges: http://badges.mariadb.org/ -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Browse the Internet in a safer fashion. Download Web of Trust: http://www.mywot.com/ Cross-platform mobile application development from MoSync: http://www.mosync.com/

3 2

Re: [Maria-discuss] [Maria-developers] Problem with MariaDb as a Windows service
by Peter Laursen 25 Nov '10

25 Nov '10

Same problem with MariaDB 5.1.51. --Peter On Sun, Nov 21, 2010 at 02:43, Vladislav Vaintroub < vladislav.vaintroub(a)oracle.com> wrote: > Hi, > It is likely this bug http://bugs.mysql.com/bug.php?id=56821 , was for > some > time in MySQL, already fixed. > > -----Original Message----- > From: maria-developers-bounces+wlad=sun.com(a)lists.launchpad.net > [mailto:maria-developers-bounces+wlad <maria-developers-bounces%2Bwlad>= > sun.com(a)lists.launchpad.net] On Behalf > Of Philip Stoev > Sent: Samstag, 20. November 2010 20:04 > To: Peter Laursen > Cc: maria-discuss(a)lists.launchpad.net; > maria-developers(a)lists.launchpad.net > Subject: Re: [Maria-developers] [Maria-discuss] Problem with MariaDb as a > Windows service > > Hi, > > It seems that the service requires the --console option to operate > properly. > > Here is how I could make it work: > > 1. In the Services Control panel, open up the properties for the service 2. > In the "Start Parameters" box, type "--console" without the quotation marks > 3. In the same dialog box, hit Start > > Philip Stoev > > ----- Original Message ----- > From: "Peter Laursen" <peter_laursen(a)webyog.com> > To: <maria-discuss(a)lists.launchpad.net>; > <maria-developers(a)lists.launchpad.net> > Sent: Saturday, November 20, 2010 3:36 PM > Subject: [Maria-discuss] Problem with MariaDb as a Windows service > > > > Some person claimed here around one week ago that MariaDB would not > > run as service after "mysqld --install". > > I replied that it worked for me - but it does not with the latest > > stable version 5.2.3 (it did with the 5.2.3 RC) (so my apology to this > > person!) > > > > Windows console output: > > > > C:\maria52\bin>sc delete maria52 > > [SC] DeleteService LYKKEDES > > > > C:\maria52\bin>mysqld --install maria52 Service successfully > > installed. > > > > C:\maria52\bin>net start maria52 > > Tjenesten maria52 starter... > > Tjenesten maria52 kunne ikke startes. > > > > Der opstod en systemfejl. > > > > Systemfejlen 1067 opstod. > > > > (From Danish --> service could not start --> the system error 1067 > > occurred) > > > > I have tried with both old datadir and the empty one shipped with > > mariaDB and also my old my.ini as well as a fresh one. > > Also I tried to add --defaults-dir to the registry (just in case I had > > overlooked a my.ini copy in C:\ or C:\Windows) and adding doublequotes > > key manually like "C:\maria52\bin\mysqld" > > --defaults-file="C:\maria52\my.ini" maria52 > > > > I double checked there are no conflicts wit all settings. > > > > The command > > "C:\maria52\bin\mysqld" --defaults-file="C:\maria52\my.ini" > > .. starts the server (also when --defaults-file is omitted) .. but not > > as a service of course. > > > > > > Was it tested with the 5.2.3 GA release that it will run as a Windows > > service? > > The RC worked as a charm - but the GA will not. Any idea? > > (I am using Win7, 64 bit, Home Premium) > > > > > > Peter > > (Webyog) > > > > > > ---------------------------------------------------------------------------- > ---- > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~maria-discuss > > Post to : maria-discuss(a)lists.launchpad.net > > Unsubscribe : https://launchpad.net/~maria-discuss > > More help : https://help.launchpad.net/ListHelp > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~maria-developers > Post to : maria-developers(a)lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-developers > More help : https://help.launchpad.net/ListHelp > >

3 2

Re: [Maria-discuss] [Maria-developers] Problem with MariaDb as a Windows service
by Alex Budovski 25 Nov '10

25 Nov '10

> Right, this was subsequently fixed in MySQL in > http://lists.mysql.com/commits/118824 > Yes, I noticed that too late.

1 0

[Maria-discuss] Problem with MariaDb as a Windows service
by Peter Laursen 20 Nov '10

20 Nov '10

Some person claimed here around one week ago that MariaDB would not run as service after "mysqld --install". I replied that it worked for me - but it does not with the latest stable version 5.2.3 (it did with the 5.2.3 RC) (so my apology to this person!) Windows console output: C:\maria52\bin>sc delete maria52 [SC] DeleteService LYKKEDES C:\maria52\bin>mysqld --install maria52 Service successfully installed. C:\maria52\bin>net start maria52 Tjenesten maria52 starter... Tjenesten maria52 kunne ikke startes. Der opstod en systemfejl. Systemfejlen 1067 opstod. (From Danish --> service could not start --> the system error 1067 occurred) I have tried with both old datadir and the empty one shipped with mariaDB and also my old my.ini as well as a fresh one. Also I tried to add --defaults-dir to the registry (just in case I had overlooked a my.ini copy in C:\ or C:\Windows) and adding doublequotes key manually like "C:\maria52\bin\mysqld" --defaults-file="C:\maria52\my.ini" maria52 I double checked there are no conflicts wit all settings. The command "C:\maria52\bin\mysqld" --defaults-file="C:\maria52\my.ini" .. starts the server (also when --defaults-file is omitted) .. but not as a service of course. Was it tested with the 5.2.3 GA release that it will run as a Windows service? The RC worked as a charm - but the GA will not. Any idea? (I am using Win7, 64 bit, Home Premium) Peter (Webyog)

2 6

[Maria-discuss] virtual columns
by Federico Razzoli 13 Nov '10

13 Nov '10

Hello I've read in the documentation that any legal SQL expression SHOULD be allowed in the Virtual Columns definition. I'm trying to use a (deterministic) stored function, but I get an error: ERROR 1642 (HY000): Function or expression is not allowed for column 'vc1' Here's my create table: CREATE TABLE t1 (c1 int, c2 int, vc1 INT AS (c1+functest()) VIRTUAL); Here's how functest() is defined: CREATE FUNCTION functest() RETURNS TINYINT DETERMINISTIC BEGIN UPDATE t2 SET c1 = c1 + 1; RETURN 0; END I think this clearly explains what I am trying to do: a function which logs accesses to a certain column. Why do I get error 1642? Is the bug in the documentation or in the software? Will future MariaDB versions allow us to create virtual columns which call stored functions? Federico

5 6

[Maria-discuss] Install as service on Windows 7 64x
by Francisco Ernesto Teixeira 11 Nov '10

11 Nov '10

Hello, First I have to say that it's a great idea. I looked for replace my MySQL servers to MariaDB, but I can't loose everything. First, when I run the downloaded MariaDB 5.2.3 as "C:\Program Files (x86)\MariaDB 5.2.3\bin\mysqld.exe" --standalone everything is allrigth. When I follow these steps on Prompt: 1. "C:\Program Files (x86)\MariaDB 5.2.3\bin\mysqld.exe" --install 2. net start mysql Says: O serviço de MySQL está sendo iniciado..... O serviço de MySQL não pôde ser iniciado. Erro de sistema. Erro de sistema 1067. O processo foi finalizado de forma inesperada. BUT, don't exists error log on Data folder or log!!! Thank you.

2 1

[Maria-discuss] Non-root install of MariaDB
by Arun Jagatheesan 05 Nov '10

05 Nov '10

Hi, Is it mandatory to be a privileged user for MariaDB? (hope not so). Is there an existing documentation or any suggestions for a non-root instal of MariaDB on Linux (CentOS)? Thanks, Arun

2 2

Re: [Maria-discuss] How to lock individual tables in 1-db-per-file binlogging (Was: Re: Per-db binlogging)
by Weldon Whipple 29 Oct '10

29 Oct '10

Dmitry, Thank you very much for your response! (I apologize for the slowness of my reply. I've been fighting a cold for several days.) See below: On Thu, Oct 21, 2010 at 11:15 PM, Dmitry Lenev <Dmitry.Lenev(a)oracle.com> wrote: > Hello Weldon! > > * Weldon Whipple <weldon(a)whipple.org> [10/10/20 00:26]: >> Thanks for the great feedback. It got me looking at the capabilities >> of MySQL 5.5. >> >> It's POSSIBLE that the new syntax: >> >> FLUSH TABLES t1, t2, t3, ... , tn WITH READ LOCK >> >> is PRECISELY the functionality we need! >> >> Our (perl) migration script MIGHT (for example) do the following: >> >> Issue the following command (implemented by me ...): >> >> 1. START BINLOG FOR DATABASE <db>; >> >> (for each database a given user owns. [Hmmm... Maybe my implementation >> allows multiple <db> arguments. I need to check.] Each database would >> start binlogging to its own file. [We will configure--in my.cnf--the >> 1-database-per-file binlogs to be stored on a very fast solid-state >> drive.]) >> >> Then the script creates a list of all tables in all the user's >> databases being migrated to another server and issues the command (new >> to MySQL 5.5): >> >> 2. FLUSH TABLES t1, t2, t3, ..., tn WITH READ LOCK; >> >> (where the tables t1, t2, ..., tn are the tables being migrated.) >> >> Then issue the following command (implemented by me ...): > > AFAIU you also want to prohibit creation of tables in this database > after this point as otherwise you can't guarantee binlog stability. > Also what about non-table objects like stored routines - don't you > want to block their modification as well? The above statement won't > provide this as it locks only *existing* *tables*. > > OTOH in my opinion it should be fairly easy to implement functionality > that you need (i.e. blocking of all DDL and DML that changes data in > database) on the basis of FLUSH TABLES <table_list> WITH READ LOCK > implementation. You just need to take database-scope S metadata lock > in addition to locking and flushing all tables in database. Such lock > will block creation of new tables and any DDL on stored routines in > the database. Maybe I need to implement a new command (something like FLUSH DATABASE db WITH READ LOCK) that--conceptually, at least--read locks all the tables in the database (like FLUSH TABLES ... WITH READ LOCK) *as well as* blocks all DDL and DML that changes data in database. I'll look through the code and find where FLUSH TABLES ... WITH READ LOCK is implemented. If I can't figure out how to "take database-scope S metadata lock," I'll get back with you... (I suppose I'll need a corresponding UNLOCK DATABASES command as well.) I've observed (and read) that the read locks are held as long as the client connection remains open, and that the UNLOCK applies to all the locks created during the same connection that created the read locks. I guess that means that our migration tool will need to maintain the connection with mysqld while it dumps (or scp's, in the case of MyISAM tables) the database snapshot. (That shouldn't necessarily be a problem--it's just something we need to be aware of. It makes sense for it to work that way.) > >> >> BUG IDENTIFIED. >> <snip/> > I have taken the liberty to report this issue as bug #57649 > (http://bugs.mysql.com/bug.php?id=57649) > > Thanks for pointing it out! Thanks for reporting it. > >> >> QUESTION: >> I read that Larry Ellison stated (at a conference) that 5.5 would be >> out by year end. How likely is that? Our company generally waits for >> some point releases before changing our customer boxes to the next >> release. >> >> Should I try to back port those locks to 5.1 in the interim? ... or >> leave well enough alone? > > I don't think it makes sense to backport metadata locks to 5.1 as it is > likely to require back-porting of too much other changes from 5.5. > > OTOH implementing what you need on top of infrastructure already present > in 5.1 is likely to require significant efforts as well. > > So I think it is better to base your work on 5.5 tree. I agree. There are quite a few major changes in 5.5. I haven't noticed meta-data-locks (MDL) before. The PSI additions to the mutex and conditions also look new. (I'm sure I'm missing lots of other changes.) (Regarding the PSI_mutex_key, PSI_rwlock_key and similar additions: I've tried to follow the patterns in 5.5 as I added my own mutexes. I'm assuming [hoping?] that they work when multiple instances of an object all refer to the same-named PSI_xxx-key ??? ...) (Is there any externally available documentation on MySQL's use of PSI?) > > Best regards, > -- > Dmitry Lenev, Software Developer > Oracle Development SPB/MySQL, www.mysql.com > > Are you MySQL certified? http://www.mysql.com/certification Not that I know of. Weldon Whipple weldon(a)whipple.org

2 2

Re: [Maria-discuss] italian translation
by Bryan Alsdorf 26 Oct '10

26 Oct '10

Hi, On 09/14/2010 11:24 PM, Colin Charles wrote: > Hi! > > On 12 Sep 2010, at 07:51, Federico Razzoli wrote: > >> Hello. >> >> I appreciate so much your new Knowledge Base. The pages that are already on line >> are very clear and complete, as the MySQL docs. But, unlike the MySQL docs, the >> Knowledge Base has free licenses. For these reasons, I would like to translate >> into italian - which is my natural language. >> >> Am I allowed to do that? As far as I understand, both the licenses used (CC >> BY-SA and GNU FDL) allow translations, as long as they have the same licenses >> used by the original work. But I want to be sure before starting. >> >> I can't translate all the articles, so I'll only translate some of the most >> interesting documents. But, as the documentation grows, maybe I may try to set >> up a group of volounteers. We'll see. > > > You are absolutely allowed to do that. You can translate it to Italian with no issue at all > > Currently (and I think, by design) it seems that kb.askmonty.org will be in the English language. Bryan (CC'ed in this email) is the right person to help setup an instance for the Italian language (something like it.kb.askmonty.org) if you were planning on making a larger translation project. It would be great if you could harness a group of volunteers We actually want to setup a structure to support translations inside our KB, I just haven't had the time to design or implement it. My two concerns are how to properly display content in another language and how to keep translated articles up to date when the English version is updated (or vice versa). If you have any ideas, please let me know. > In the meantime however, as you'd like to just translate interesting documents, just go ahead, translate them, and it would rock if you'd point folk to the English version at the askmonty KB > > Good luck with your translation work and tell us if you need any help! Yes please let us know if there is anything we can do to help. I will try to work on supporting other languages soon since people are actually translating articles. Best Regards, -- Bryan Alsdorf, Lead Web Developer Monty Program AB. http://montyprogram.com

4 4

Re: [Maria-discuss] How to lock individual tables in 1-db-per-file binlogging (Was: Re: Per-db binlogging)
by Weldon Whipple 19 Oct '10

19 Oct '10

Davi, Sergei (and everyone else), Thanks for the great feedback. It got me looking at the capabilities of MySQL 5.5. It's POSSIBLE that the new syntax: FLUSH TABLES t1, t2, t3, ... , tn WITH READ LOCK is PRECISELY the functionality we need! Our (perl) migration script MIGHT (for example) do the following: Issue the following command (implemented by me ...): 1. START BINLOG FOR DATABASE <db>; (for each database a given user owns. [Hmmm... Maybe my implementation allows multiple <db> arguments. I need to check.] Each database would start binlogging to its own file. [We will configure--in my.cnf--the 1-database-per-file binlogs to be stored on a very fast solid-state drive.]) Then the script creates a list of all tables in all the user's databases being migrated to another server and issues the command (new to MySQL 5.5): 2. FLUSH TABLES t1, t2, t3, ..., tn WITH READ LOCK; (where the tables t1, t2, ..., tn are the tables being migrated.) Then issue the following command (implemented by me ...): 3. SHOW DATABASE BINLOG STATUS; which shows--for each database being binlogged to its own file: a. the database name b. whether binlogging is active c. the name of the current binlog file d. the binlog position in that file. The script captures the coordinates, then 4. Creates a copy of the database(s) using mysqldump or scp/tar/gzip, etc. (MyISAM databases will probably just be copied "raw," because it is much faster. Innodb will probably have to use mysqldump or something similar.) 5. UNLOCK TABLES: On the new server, the copied/mysqldump'ed files will be used to bring up the mysql on the new server. At some future time--hopefully SOON--the tables could be locked again. For any where the coordinates have changed: The binlog file(s) would be copied to the new server, "played" by mysqlbinlog, and the new server would be brought online on the new box and taken offline on the old. When the migration is determined to be complete, issue this command (implemented by me) on the old box: 6. STOP BINLOG FOR DATABASE <db>; for all the user's databases ... and the migration is done. QUESTIONS/ASSUMPTIONS: 1. In playing with the new FLUSH TABLES t1, t2, ..., tn command, I've noticed that if the connection drops, the locks are all unlocked. ... So our scripts will have to make sure the connection stays up. (ANY SUGGESTIONS?) 2. The UNLOCK TABLES command unlocks all the tables locked earlier in the same session. (So it doesn't need the variable argument list of tables to unlock ...) A post on dev.mysql.com shows the following possible sequence of commands: FLUSH TABLES WITH READ LOCK; SHOW MASTER STATUS; SYSTEM xfs_freeze -f /var/lib/mysql; SYSTEM YOUR_SCRIPT_TO_CREATE_SNAPSHOT.sh; SYSTEM xfs_freeze -u /var/lib/mysql; UNLOCK TABLES; EXIT; (The FLUSH TABLES command would correspond to #2 above. SHOW MASTER STATUS would correspond to #3 above. UNLOCK TABLES would correspond to #5 above. The SYSTEM commands would have to be replaced by our own commands/scripts.) Would running (sub-)scripts from SYSTEM commands inside MySQL be sufficient to hold the locks? BUG IDENTIFIED. I noticed the following mysqld-crashing bug--in 5.5.6 rc as well as the one I modified: 1. FLUSH TABLES t1, t2, t3, ..., tn WITH READ LOCK; 2. FLUSH TABLES; The second FLUSH TABLES (with no added tokens) crashes at mdl.cc:1563 : DBUG_ASSERT(mdl_request->type != MDL_EXCLUSIVE || is_lock_owner(MDL_key::GLOBAL, "", "", MDL_INTENTION_EXCLUSIVE)); because is_lock_owner() returns NULL when FLUSH TABLES is called immediately after FLUSH TABLES [with additional args]; QUESTION: I read that Larry Ellison stated (at a conference) that 5.5 would be out by year end. How likely is that? Our company generally waits for some point releases before changing our customer boxes to the next release. Should I try to back port those locks to 5.1 in the interim? ... or leave well enough alone? Thanks in advance for your feedback/help/advice!! We.don Whipple On Mon, Oct 18, 2010 at 12:48 PM, Davi Arnaut <davi.arnaut(a)oracle.com> wrote: > On 10/18/10 3:16 PM, Weldon Whipple wrote: >> >> Well, I finished a working prototype that does everything except the >> locking and unlocking of databases. Someone mentioned that it's now >> possible to lock individual tables. Would you--anyone--be willing to >> point me toward places in the 5.5 code that use that >> locking/unlocking? >> > > Do you want to lock the database, or individual tables, or both? Anyway, > take a look at mysql_rm_db as the locking is all very similar. Roughly, the > algorithm of a DROP DATABASE is: > > // Protect against other schema operations > lock_schema_name("db1"); > // Build list of tables in the db1 directory > table_list = .. > // Initialize metadata lock request > table_list->mdl_request.init(MDL_key::TABLE, > table_list->db, > table_list->table_name, MDL_EXCLUSIVE); > // Lock tables > lock_table_names(thd, tables, NULL ...) > // Remove from cache and drop the table... > > The best thing at this point is to study (and debug) a similar statement and > understand how metadata locks work (mdl prefix) or how tables are > open/locked. > > Regards, > > Davi > > -- > MySQL Internals Mailing List > For list archives: http://lists.mysql.com/internals > To unsubscribe: http://lists.mysql.com/internals?unsub=weldon@whipple.org > >

1 0

Re: [Maria-discuss] How to lock individual tables in 1-db-per-file binlogging (Was: Re: Per-db binlogging)
by Weldon Whipple 18 Oct '10

18 Oct '10

Davi, Thanks for the pointers! I'd like to lock an entire database. (I guess I can iterate through the tables in database if that's the only way. [I suppose there might be possible locking issues to deal with ...]) I'll look at the source you recommend ... Weldon weldon(a)whipple.org On Mon, Oct 18, 2010 at 12:48 PM, Davi Arnaut <davi.arnaut(a)oracle.com> wrote: > On 10/18/10 3:16 PM, Weldon Whipple wrote: >> >> Well, I finished a working prototype that does everything except the >> locking and unlocking of databases. Someone mentioned that it's now >> possible to lock individual tables. Would you--anyone--be willing to >> point me toward places in the 5.5 code that use that >> locking/unlocking? >> > > Do you want to lock the database, or individual tables, or both? Anyway, > take a look at mysql_rm_db as the locking is all very similar. Roughly, the > algorithm of a DROP DATABASE is: > > // Protect against other schema operations > lock_schema_name("db1"); > // Build list of tables in the db1 directory > table_list = .. > // Initialize metadata lock request > table_list->mdl_request.init(MDL_key::TABLE, > table_list->db, > table_list->table_name, MDL_EXCLUSIVE); > // Lock tables > lock_table_names(thd, tables, NULL ...) > // Remove from cache and drop the table... > > The best thing at this point is to study (and debug) a similar statement and > understand how metadata locks work (mdl prefix) or how tables are > open/locked. > > Regards, > > Davi > > -- > MySQL Internals Mailing List > For list archives: http://lists.mysql.com/internals > To unsubscribe: http://lists.mysql.com/internals?unsub=weldon@whipple.org > >

1 0

[Maria-discuss] How to lock individual tables in 1-db-per-file binlogging (Was: Re: Per-db binlogging)
by Weldon Whipple 18 Oct '10

18 Oct '10

Thanks, Sergei and everyone else, for your feedback/ideas! Well, I finished a working prototype that does everything except the locking and unlocking of databases. Someone mentioned that it's now possible to lock individual tables. Would you--anyone--be willing to point me toward places in the 5.5 code that use that locking/unlocking? I'm interested in sharing the changes with the community if there is any interest. (Any suggestions about whether I should prefer launchpad versus forge.mysql.com or some other place to share? [I once owned a project on SourceForge--I think it's still there, but not very active ...]. :-) A few comments in response to your comments: On Thu, Sep 16, 2010 at 6:34 AM, Sergei Golubchik <serg(a)askmonty.org> wrote: > Hi, Weldon! > > On Sep 15, Weldon Whipple wrote: >> >> > See where mysql_bin_log.write is called. >> >> Excellent information! (I was hoping it might be that easy ???). If I >> succeed in making a DB_BIN_LOG class derive from MYSQL_BIN_LOG (with an >> instance of DB_BIN_LOG for each database that is currently binlogging), >> I could--in theory, at least--just call something like >> db_binlog->write () at those places. > > Better make this write method virtual and implement it in your derived > class. I did implement it as a derived class, but it was a bit more work than just reimplementing the ::write() method. (I use separate instances of DB_BINLOG--the derived class--for each database that is binlogging to its separate binlog file [sequence].) I had to have a few additional methods (extremely small) to set up for opening files named <database>-bin.<seq#>, <database>-bin.index, etc. I also maintain a db_binlog.info file that remembers the databases being binlogged across restarts. One major change was in the way the global MYSQL_BIN_LOG class is referenced. In the original code, it comes into existence at the top of binlog.cc. Before I started making my modifications, I changed MYSQL_BIN_LOG to be a pointer to MYSQL_BIN_LOG, declared in mysqld.cc (and extern'ed in mysqld.h). At the point in mysqld.cc where mysql_bin_log is first referenced I "new" the global instance of MYSQL_BIN_LOG*. I went through all the files that reference mysql_bin_log and made the necessary changes so that mysql_bin_log works as a pointer. (Example: Change "mysql_bin_log.is_active()" to "mysql_bin_log->is_active().) Also, before, referencing mysql_bin_log*, I always make sure it is non-NULL ... Then I made my changes for 1 db-per-file binlogging, using #ifdef HAVE_DB_BINLOG/#endif blocks to allow building with or without 1-db-per-file binlogging. As I'm typing this post, I'm running mysql-test-run.pl on a build without HAVE_DB_BINLOG defined and it seems to be passing all the tests. I need to write additional test cases for when HAVE_DB_BINLOG is defined ... Thanks in advance for ideas/suggestions (as well as for the ideas in the past). Weldon Whipple weldon(a)whipple.org (I'll leave the conversations below to help refresh your memory on this thread's past.) > >> >> Questions I Have. >> >> ---------------- >> >> >> >> 1. I notice that binlog is in the list of engines and plugins >> >> (displayed by SHOW ...). The bottom of log.cc has >> >> "mysql_declare_plugin(binlog)". Do I need one for db_plugin? >> >> (probably not?) >> > >> > depends. >> > binlog needs to be declated a plugin, to be able to pretent being a >> > storage engine, to be able to force two phase commit (2PC). >> > >> > 2PC is used to commit or rollback a transaction atomically in more >> > than one engine. And MySQL only uses 2PC when a transaction spans >> > more than one engine. But we want a transaction to be committed in >> > the engine and written to a binlog - and it should be done >> > atomically too. So, binlog pretends to be an engine, pretends to >> > participate in a transaction, which forces MySQL to use 2PC which >> > can guarantee that a transaction is either committed and written to >> > a binlog - or not committed and not written. Reliably, even if MySQL >> > crashes in the middle. >> > >> > So, if you don't use innodb, or don't use >> > innodb_flush_log_at_trx_commit=1 or don't use sync_binlog=1 you >> > probably don't need to support 2PC as your setup is not crash proof >> > anyway. >> > >> > If you care about innodb<->binlog consistency in the presence of >> > crashes, you should support 2PC in your binlog, as explained above. >> >> We DO have a small percentage of innodb databases. If 2PC commits >> (rolls back, etc.) atomically to more than one engine, does that mean >> TWO (only)? ... or could it happen for three (specifically, innodb, >> MYSQL_BIN_LOG's binlog, and DB_BIN_LOG's binlog)? > > See http://en.wikipedia.org/wiki/Two-phase_commit_protocol > > It's two phases, not two engines, any number of engines can participate > in a transaction. > > But! All of them but one have to support two-phase commit. Binlog does > not support it. Apparently, DB_BIN_LOG will not support it either - > adding two-phase commit support to binlog will surely be beyond the > scope of your work. > > It means, you cannot have InnoDB, binlog, and DB_BIN_LOG to participate > in a two-phase commit. But you can disable MYSQL_BIN_LOG altogether and > only use DB_BIN_LOG - in that case you can have a two-phase commit > between DB_BIN_LOG and InnoDB. > >> The two kinds of binlog files would have the same format (except that >> one is for only one database). Are they considered two storage >> engines/plugins? > > If you want to write to both - yes. A transaction will need to be > written to both independently, so you want them to be in sync, and MySQL > uses 2PC to synchronize different data storages. > > You can solve that by > > 1) not using MYSQL_BIN_LOG. In this case there's only InnoDB and > DB_BIN_LOG to keep in sync, and InnoDB can do 2PC. > > 2) not making DB_BIN_LOG independent from MYSQL_BIN_LOG. For example, > everything is written to binlog only. Then you have a background > thread (or even a separate process) that reads binlog and writes your > per-db binlogs. In that case you have only InnoDB and MYSQL_BIN_LOG > to keep in sync, and MySQL already does that. Your background thread > is only catching up, it is allowed to fall behind. > >> (I notice that the "mysql_declare_plugin(binlog)" declaration is at >> the bottom of log.cc. Most of the other storage engines' corresponding >> declarations are in files in the storage subdirectories. If I were to >> need a "mysql_declare_plugin(db_binlog)" declaration, could it also go >> at the bottom of log.cc? ... Or (since a DB_BIN_LOG is AKO [a kind of] >> MYSQL_BIN_LOG [in the OO sense]), are MYSQL_BIN_LOGs and DB_BIN_LOGs >> both kinds of binlog plugins ...? > > if you want to have two plugins in one file you still need to use one > mysql_declare_plugin(), not two. See example at the end of > http://www.packtpub.com/article/look-inside-mysql-daemon-plugin > > Regards, > Sergei >

1 0

[Maria-discuss] WL #47
by Oleg Tsarev 13 Oct '10

13 Oct '10

Hello Maria! https://code.launchpad.net/~percona-dev/percona-server/release-5.1.49-12-rnt When i build this branch: cd Percona-Server/ && ./BUILD/autorun.sh && ./configure --prefix=/usr/local/mysql --exec-prefix=/usr/local/mysql --bindir=/usr/local/mysql/bin --sbindir=/usr/local/mysql/bin --sysconfdir=/etc --datadir=/usr/local/mysql/share --includedir=/usr/local/mysql/include --libdir=/usr/local/mysql/lib --libexecdir=/usr/local/mysql/bin --with-client-ldflags=-all-static --localstatedir=/var/lib/mysql --sharedstatedir=/usr/local/mysql/com --mandir=/usr/local/mysql/man --infodir=/usr/local/mysql/share/info --enable-shared --enable-static --enable-assembler --enable-local-infile --with-mysqld-user=mysql --with-unix-socket-path=/var/lib/mysql/mysql.sock --with-pic --with-extra-charsets=complex --with-ssl --enable-thread-safe-client --with-readline --without-plugin-ndbcluster --without-plugin-maria --without-plugin-innobase --with-plugin-innodb_plugin --with-plugin-partition --with-plugin-csv --with-plugin-archive --with-plugin-blackhole --with-plugin-federated --without-embedded-server --without-bench --with-zlib-dir=bundled --with-big-tables && make -j3 And then run tests: cd mysql-test && ./mysql-test-run main.ctype_cp932_binlog_stm I get test error: worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009 main.ctype_cp932_binlog_stm [ fail ] Found warnings/errors in server log file! Test ended at 2010-10-13 08:02:25 line 101013 18:02:25 [ERROR] Error in Log_event::read_log_event(): 'Event too big', data_len: 50724864, event_type: 0 ^ Found warnings in /mnt/data/home/oleg.tsarev/12687/Percona-Server/mysql-test/var/log/mysqld.1.err ok - saving '/mnt/data/home/oleg.tsarev/12687/Percona-Server/mysql-test/var/log/main.ctype_cp932_binlog_stm/' to '/mnt/data/home/oleg.tsarev/12687/Percona-Server/mysql-test/var/log/main.ctype_cp932_binlog_stm/' ------------------------------------------------------------ The servers were restarted 0 times Spent 0.000 of 1 seconds executing testcases mysql-test-run: WARNING: Got errors/warnings while running tests, please examine '/mnt/data/home/oleg.tsarev/12687/Percona-Server/mysql-test/var/log/warnings' for details. Completed: Failed 1/1 tests, 0.00% were successful. Failing test(s): main.ctype_cp932_binlog_stm I found, what reason of this bug - our patch wl47.patch. I try to fix this bug, but i know replication not enough for this. Do you know about this trouble with WL #47? Best regards, Oleg --- Oleg Tsarev, Software Engineer, Percona Inc.

1 0

[Maria-discuss] improving the thread/connection pool
by MARK CALLAGHAN 11 Oct '10

11 Oct '10

I think more work needs to be done on the MariaDB thread/connection pool. Does a worklog exist for that? The problems are: * multi-core performance * stalled threads stall the pool This is based on my review and testing of the feature in MySQL 6.0 and quickly browsing the code in MariaDB. I also fixed multi-core performance as a proof of concept but don't have access to that patch. The multi-core performance problem occurs because only one event_base instance is used (see sql/scheduler.cc). Note that memcache uses one per CPU core. This is a big source of mutex contention. An additional problem is that EPOLLONESHOT is not used. I don't know if libevent supports that yet. Were it used one less interaction with libevent would be needed per query. I reported the performance issue at http://bugs.mysql.com/bug.php?id=42288 An interesting decision when there are multiple event_base instances is whether the mapping between an event_base instance and connections is fixed. If it is fixed then there is less libevent work to do per-query and there will be less mutex contention. But if connections cannot migrate between event_base instances per query then there will be cases where too many pending queries wait for one and no pending queries exist for others. I think that stalls are another problem to fix. When a user connection blocks on a row lock wait or another internal locks (and calls THD::enter_cond), then this is an opportunity to count this connection as not running and schedule another thread. This isn't a trivial problem to fix because it might require a new thread to be created. There is also the issue of what to do when another connection has been scheduled. In that case does the thread that just became runnable get to run immediately? If it was just granted a row lock or other lock then we want it to run right away. But that might cause X+1 threads to be running in the thread pool when the limit is X. The difference between X and X+1 is small. But this could lead to 2*X threads running. What is the limit? -- Mark Callaghan mdcallag(a)gmail.com

1 0

[Maria-discuss] MariaDB 5.2.2-gamma
by Daniel Bartholomew 29 Sep '10

29 Sep '10

All, MariaDB 5.2.2-gamma source and binary tarballs, and packages for various operating systems and Linux distributions are now available for download: http://askmonty.org/wiki/MariaDB:Download:MariaDB_5.2.2-gamma See also: Release Notes: http://kb.askmonty.org/v/mariadb-522-release-notes Changelog: http://kb.askmonty.org/v/mariadb-522-changelog Thanks. -- Daniel Bartholomew Monty Program - http://askmonty.org

3 3

[Maria-discuss] MariaDB Knowledgebase typo
by Yousif Masoud 16 Sep '10

16 Sep '10

Hi, I'd like to thank everyone working on this project. MariaDB is currently installed on one of my Dev environments, I am looking forward to switching to it. I noticed there was a minor typo on: http://kb.askmonty.org/v/compiling-with-the-innodb-plugin-from-oracle First sentence reads: Normally MariaDB comes with XtraDB <http://kb.askmonty.org/v/xtradb-storage-engine>, an enhanced version **if** the InnoDB plugin that comes from Oracle. I believe it should be: Normally MariaDB comes with XtraDB <http://kb.askmonty.org/v/xtradb-storage-engine>, an enhanced version **of** the InnoDB plugin that comes from Oracle. Many thanks, Yousif PS. I don't know if there is a formal method for reporting this. Please accept my apologies if this is not the best way to do it.

2 1

Re: [Maria-discuss] Seeking command syntax feedback (Still Re: Per-db binlogging)
by Weldon Whipple 16 Sep '10

16 Sep '10

On Wed, Sep 15, 2010 at 2:00 PM, Sergei Golubchik <serg(a)askmonty.org> wrote: > Hi, Weldon! Hi, Sergei! > > On Sep 15, Weldon Whipple wrote: <snip/> >> 2. FLUSH TABLES WITH READ LOCK FOR DATABASE dbname; >> >> (I just added an optional 'FOR DATABASE dbname' to the already >> existing command--which still works, BTW. Is this a misuse of the word >> "FOR"?) >> This is the command that locks the tables before someone (some >> program) dumps/copies the tables that will be moved to another server. >> It flushes and locks only one database. > > This would be difficult to implement. > > FLUSH TABLES WITH READ LOCK is not implemented in a way that can be > generalized to support per-database locks :( I had guessed as much. (The method in my DB_BINLOG_MGR method that implements that functionality consists of a mutex lock, a comment about some sort of miracle happening, then a mutex unlock.) I wonder if there might be a way of inhibiting some user database (temporarily) from changing ... Alternately, I suppose we could do a global FLUSH TABLE WITH READ LOCK/ UNLOCK TABLES. Or ... (???) > Besides, I personally wouldn't worry much about the syntax. It's > something you can easily change anytime - e.g. replace BINLOG with > BINLOGGING or FOR with something else. Yeah, every time I write a new prototype I tweak the syntax a bit. At the moment I'm just trying to settle on an implementation that would work for our company (and still be of some sort of general use). > > Regards, > Sergei > Thanks, Weldon

1 0

Re: [Maria-discuss] Per-db binlogging
by MARK CALLAGHAN 16 Sep '10

16 Sep '10

+maria-discuss as they are working in replication too +robert.hodges as tungsten replicator has features that could be used here I am very interested in a subset of this. I want one SQL thread per database on a slave (stream per database on the slave). However I don't need to split the binlog on the master to get that and writing a binlog file per database on the master might complicate the sync_binlog option that keeps the binlog and InnoDB in sync during crash recovery. How will this work in that case? Note that a stream (SQL slave thread) per database on the slave will break rpl_transaction_enabled. Some of us rely on that to keep slaves consistent during crash recovery. I assume you don't use that feature. MySQL has worklogs to use db tables in place of relay-log.info and when that code is production ready, then this is not a problem. On Mon, Sep 13, 2010 at 1:52 PM, Weldon Whipple <weldon(a)whipple.org> wrote: > Greetings! > > My employer has asked me to implement per-DB binlogging for > MySQL. I've been working on prototypes for 3-4 weeks now, and decided > it's time to post to this list to ask for comments, suggestions, > condolences, etc. (I've been a "lurker" for quite awhile. I hope this > post isn't too far off the mark) The assignment is *only* for master-side > binlogging. (It doesn't require a slave/replication-side implementation.) > > > Why I Want to Do It. > ------------------- > > I work for an ISP that hosts (last I heard--I HOPE I'm not lying) over > 2 million domains. Customers are allowed to have (almost) unlimited > MySQL databases. Migrating an account from one physical server to > another is a daunting task. (A typical server has easily 2000+ > [sometimes far more] databases.) Global mysqld binlogging isn't > feasible when we want to migrate (for example) a single account to > another server. > > Our proposed scenario goes something like this: > > 1. START USER BINLOG FOR DATABASE <db> > 2. FLUSH USER TABLES WITH READ LOCK FOR DATABASE <db> > 3. SHOW USER BINLOG STATUS [WHERE DATABASE LIKE <pattern>] > > SHOW output might look something like: > ================================= > mysql> show user binlog status; > +----------------------+----------+---------------------------------+------------+ > | Database | User | Binlog_file | > Binlog_pos | > +----------------------+----------+---------------------------------+------------+ > | booklibs | wwhipple | booklibs-bin.000003 | > 248 | > | charmins_gravestones | charmins | charmins_gravestones-bin.000001 | > 4 | > +----------------------+----------+---------------------------------+------------+ > 2 rows in set (0.01 sec) > > The "where" clause also works: > > mysql> show user binlog status where user like 'charmins'; > +----------------------+----------+---------------------------------+------------+ > | Database | User | Binlog_file | > Binlog_pos | > +----------------------+----------+---------------------------------+------------+ > | charmins_gravestones | charmins | charmins_gravestones-bin.000001 | > 4 | > +----------------------+----------+---------------------------------+------------+ > 1 row in set (0.01 sec) > ================================= > > At this point the migration tools note the binlog coordinates and > start copying the databases to the new server. (For myisam tables, the > tools writers want to just copy [scp?] the files. For innodb, they > will use something like mysqldump.) > > (Note: We might want to "lose" the "User" column in the above table] > in our recent designs.) > > Then the sequence of MySQL commands resumes: > > 4. UNLOCK USER BINLOG FOR DATABASE <db> > > Finally, when migration is complete: > > 5. STOP USER BINLOG FOR DATABASE <db> > > A high percentage of users (infrequent bloggers, etc.) go several days > (sometimes even weeks or months) without updating their databases. For > them--after migrating the files to the new server, a final check of > the binlog coordinates on the old box can verify that nothing has > changed. > > If it HAS changed, migration can copy the binlog file(s) to the new > box and use the mysqlbinlog command (specifying the starting > coordinates) to bring the new database in sync with the old one. > > (This scenario is probably oversimplified, ignoring things like DNS > caching, TTL, etc., etc. Hopefully it doesn't include too many lies.) > > > How I Plan to Do It. > ------------------- > > I've noticed that: > > 1. The class MYSQL_BIN_LOG seems to be involved in most binlogging > 2. MYSQL_BIN_LOG inherits from TC_LOG and MYSQL_LOG. It is created in > mysqld.cc at startup. > > My current partial implementation has: > > 1. Class DB_BIN_LOG inheriting from MYSQL_BIN_LOG, adding members like > db_name > db_binlog_name > db_index_name > and methods to access them, etc. > > 2. Singleton class USER_BIN_LOG_MGR. (Should probably be DB_BIN_LOG_MGR), > which maintains a db_binlog_hash of information about each DB being > binlogged. A DB_BIN_LOG_ENTRY (in the hash) contains: > dbname > locked (bool)--has it been locked by FLUSH ... TABLES WITH READ LOCK? > binlog file > binlog_pos > is_active > a pointer to a DB_BIN_LOG instance > > USER_BINLOG_MGR has a rw lock to protect access to its hash of > currently binlogging db's. (Most accesses will probably be > read-only?) > > Is it plausible to identify all places where a binlog addition might > occur? In those places, if the singleton USER_BIN_LOG_MRG exists, ask > it if the current DB is being binlogged. If so, send the request to > the DB_BIN_LOG instance. > > > Questions I Have. > ---------------- > > 1. I notice that binlog is in the list of engines and plugins > (displayed by SHOW ...). The bottom of log.cc has > "mysql_declare_plugin(binlog)". Do I need one for db_plugin? > (probably not?) > 2. I've diagrammed the binary log event taxonomy--the 24 classes that > inherit from Log_event (in log_event.cc/h). That was my main > motivation for wanting to inherit from MYSQL_BIN_LOG. > 3. On the other hand, I wonder if inheriting from MYSQL_BIN_LOG might > be overkill for "master only" binlogging--without the > slave/replication part of it. > 4. What version should I be working on? (We're currently running > 5.1.47.) What should I check out of bzr/launchpad? (Is that still > what we're doing with the changes in ownership?) > 5. I see that THD is involved in binlogging. (Several THD methods are > defined in log.cc.) Are there any caveats here? > 6. What files should I use? A new h/cc pair? ... or just add to the > hierarchy in log.h/cc? > > In an ideal world, it would be nice to inherit polymorphically from > MYSQL_BIN_LOG, overriding methods that set the names of the binlog > file and index file (etc.) then just call the methods and have it do > the "right thing." On the other hand, I get the impression that I > might be oversimplifying. > > I welcome your advice!! > > What I've Implemented So Far (about 13 Prototypes). > -------------------------------------------------- > > (PRELIMINARY NOTE:) > > Our initial plan was to call it "Per-User Binlogging". The user here > is a cPanel [control panel] user. cPanel's database naming convention > is to have all of a user's database names start with the username, > followed by an underscore, followed by a distinctive database > name. Thus all the commands above start with > > <verb> USER ... > > Originally most of them could end either "DATABASE <db>" or "USER > <user>" (with user meaning cPanel user). Thus, in the original plan > the first command above was: > > START USER BINLOG FOR (USER <user> | DATABASE <db>) > > We have realized that per-database binlogging is all we really need. > We imagine that others in our situation might want something similar. > Since not everyone uses cPanel, we should forget per[cPanel]-user > binlogging, focusing on per-database binlogging. > > I have several versions of lex and bison/yacc files (sql_yacc.yy, > lex.h) to implement the above (and earlier variants). The recent > versions avoid increasing the %expect'ed 169 shift/reduce conflicts > specified in sql_yacc.yy. > > (END OF PRELIMINARY NOTE) > > I currently have 13 different Subversion branches with different > (partial) implementations. > > 1. All have some lex/bison grammer defined. (I'm not completely > satisfied with any of them.) > > 2. Per-db binlogging is enabled by two my.cnf (or command-line) > options: > > user_binlog_dir=/full/directory/path > user_binlog_persist_file=user_binlog.info > > Our servers have fast solid-state drives that we will use for per-db > binlogging. We want to specify a separate directory to store all the > per-db binlogs > > The persist_file stores information about the current state of > db-binlogging--to survive a restart. > > Just about every instance of "user_binlog" in this note should > probably be changed to "db_binlog" ... (???) > > 3. I have added cases in sql_parse.cc for > > SQLCOM_START_USER_BINLOG_DB: > SQLCOM_FLUSH_AND_LOCK_DB: > SQLCOM_SHOW_USER_BINLOG_STATUS: > SQLCOM_UNLOCK_DB: > SQLCOM_STOP_USER_BINLOG_DB: > > (as well as some "USER" variants like SQLCOM_START_USER_BINLOG_USER:, > which should probably abandoned.) > > They should probably be changed to something like: > > SQLCOM_START_DB_BINLOG: > SQLCOM_FLUSH_AND_LOCK_DB: > SQLCOM_SHOW_DB_BINLOG_STATUS: > SQLCOM_UNLOCK_DB: > SQLCOM_STOP_DB_BINLOG: > > ----------------- > > Now that you've read it, please feel free to throw darts, etc. At this > point I'm willing to discard everytning and start over. (In the worst > case--if everyone on this list thinks per-db binlogging is a terrible > idea--I guess I'll be forced to create our own patch [sigh].) > > On the other hand, I would love to help contribute to this effort. (If > per-db binlogging is already underway, let me know, and I'll likely help.) > Thanks in advance for feedback/suggestions/help. Feel free to contact > me privately if you want to. > > Weldon Whipple > weldon(a)whipple.org > > -- > MySQL Internals Mailing List > For list archives: http://lists.mysql.com/internals > To unsubscribe: http://lists.mysql.com/internals?unsub=mdcallag@gmail.com > > -- Mark Callaghan mdcallag(a)gmail.com

3 2

[Maria-discuss] italian translation
by Federico Razzoli 12 Sep '10

12 Sep '10

Hello. I appreciate so much your new Knowledge Base. The pages that are already on line are very clear and complete, as the MySQL docs. But, unlike the MySQL docs, the Knowledge Base has free licenses. For these reasons, I would like to translate into italian - which is my natural language. Am I allowed to do that? As far as I understand, both the licenses used (CC BY-SA and GNU FDL) allow translations, as long as they have the same licenses used by the original work. But I want to be sure before starting. I can't translate all the articles, so I'll only translate some of the most interesting documents. But, as the documentation grows, maybe I may try to set up a group of volounteers. We'll see. Regards, Federico

2 1

[Maria-discuss] Mac package (was Re: Contact Form - []: jeremy ellison)
by Hakan Kuecuekyilmaz 26 Aug '10

26 Aug '10

Hi Jeremy, all, On 16.08.2010, at 12:47, Bo Thorsen wrote: > Den 14-08-2010 05:25, Contact Form skrev: >> Looks interesting, why do you not have a mariadb package for Apple >> Mac OS X? This is the basis for my blog, bb, and server backend. If >> you have no Mac support it's not a drop in replacement for MYSQL. > > Hi Jeremy, > > The reason is that no one has offered to do it yet. MariaDB isn't a product sold by Monty Program, but an open source community project. Us Monty Program guys do a lot of the work, though. > > If someone will contribute the necessary work to get Mac packages, they will be included. Until then, it's source code only. Should you be interested in doing this, or know someone who will, then you should ask about the necessary work on the mailing list > maria-discuss(a)lists.launchpad.net. I read about your request for a MariaDB package for Mac OS X on my vacation and did some research. Back from vacation I have an alpha version of MariaDB package for Mac OS X for you and for our community to test. Caution: this is the first installer I wrote on Mac, so do not use it on a production system. Please test the installer and provide us with feedback. Known issues in the MariaDB installer: * The Preferences Pane app for starting/stopping the server instance is missing * The installer for setting up MariaDB as a Startup Item is missing. Side node: while digging into the Mac installer I found two bugs in the MySQL Mac OS X installer. * http://bugs.mysql.com/bug.php?id=56279 Mac installer does not work as documented * http://bugs.mysql.com/bug.php?id=56280 Mac installer's postflight script does not work all the time You can grab the package from here: http://lisas.de/~hakan/file/mariadb-5.1.49-osx10.6-x86.pkg Best, Hakan -- Hakan Küçükyılmaz, QA/Benchmark Engineer, Stuttgart/Germany Monty Program Ab, http://askmonty.org/ Skype: hakank_ Phone: +49 171 1919839

1 0

[Maria-discuss] Clustering with Maria/Aria engine
by Joshua Partogi 26 Aug '10

26 Aug '10

Hi all, Does Maria/Aria engine supports clustering? Or do we still have to use NDB for this? Thanks for your help. Kind regards, Joshua. -- http://twitter.com/scrum8

3 4

[Maria-discuss] mariadb-mysql command-line problem on CentOS 5.5 i386
by Daniel Bartholomew 24 Aug '10

24 Aug '10

I saw a comment today from Eric Koh on the Knowledgebase article for the mysql Command-line Client: http://kb.askmonty.org/v/mysql-command-line-client --------------------------------------------------------------------- mariadb-mysql command-line problem on CentOS 5.5 i386 I tried these 2 RPMs MariaDB-client-5.1.42-68.el5.i386.rpm MariaDB-client-5.1.49-82.el5.i386.rpm I get this message when starting the mysql client mysql: symbol mysql_get_server_name, version libmysqlclient_16 not defined in file libmysqlclient.so.16 with link time reference running ldconfig/rebooting doesnt help. The RPMs for the server are fine though. I am thus using MariaDB-server and MariaDB-shared together with MySQL-client-community --------------------------------------------------------------------- Anyone know what might be going on here? Thanks. -- Daniel Bartholomew Monty Program - http://askmonty.org

4 6

[Maria-discuss] my_atomic_add64
by Oleg Tsarev 24 Aug '10

24 Aug '10

Hello, I need my_atomic_add64 in mysql. Can i simple add following macros, or i need more advanced tricks? tsarev@main:/storage/project/percona/rtd_2$ diff -Nur ../rtd/c/include/my_atomic.h c/include/my_atomic.h --- ../rtd/c/include/my_atomic.h 2010-07-09 16:35:11.000000000 +0400 +++ c/include/my_atomic.h 2010-08-17 18:57:07.648819066 +0400 @@ -96,25 +96,30 @@ make_atomic_cas( 8) make_atomic_cas(16) make_atomic_cas(32) +make_atomic_cas(64) make_atomic_cas(ptr) make_atomic_add( 8) make_atomic_add(16) make_atomic_add(32) +make_atomic_add(64) make_atomic_load( 8) make_atomic_load(16) make_atomic_load(32) +make_atomic_load(64) make_atomic_load(ptr) make_atomic_store( 8) make_atomic_store(16) make_atomic_store(32) +make_atomic_store(64) make_atomic_store(ptr) make_atomic_swap( 8) make_atomic_swap(16) make_atomic_swap(32) +make_atomic_swap(64) make_atomic_swap(ptr) #undef make_atomic_add --- Oleg Tsarev, Software Engineer, Percona Inc.

3 4

[Maria-discuss] Decimal operations
by Oleg Tsarev 23 Aug '10

23 Aug '10

Hello, I don't understand how right work with decimal type. As you talk, i change column types from CHAR(...) to DECIMAL in my patch: http://www.percona.com/docs/wiki/patches:response_time_distribution Now i have trouble with decimal precision/scale. Here is my definition of system table INFORMATION_SCHEMA.QUERY_RESPONSE_TIME: ST_FIELD_INFO query_response_time_fields_info[] = { {"TIME", MY_INT64_NUM_DECIMAL_DIGITS, MYSQL_TYPE_LONGLONG, 0, MY_I_S_UNSIGNED, "time", SKIP_OPEN_TABLE }, {"COUNT", MY_INT32_NUM_DECIMAL_DIGITS, MYSQL_TYPE_LONG, 0, MY_I_S_UNSIGNED, "count", SKIP_OPEN_TABLE }, {"TOTAL", MY_INT64_NUM_DECIMAL_DIGITS, MYSQL_TYPE_LONGLONG, 0, MY_I_S_UNSIGNED, "total", SKIP_OPEN_TABLE }, {0, 0, MYSQL_TYPE_STRING, 0, 0, 0, SKIP_OPEN_TABLE } }; So, i want use DECIMAL(20,6) for columns time and total, and DECIMAL(14,0) for columns count. 1) Does above definiton correct, or should include some information about precision/scale? I collect time of query execution in: 1) Column total - in int64, microseconds count 2) Column count - in int64, just count Here is source code, for fill this table: for(int i= 0, count= m_utility.bound_count() + 1 /* with overflow */; count > i; ++i) { const uint64 time = m_utility.bound(i); const int64 count = m_time.count(i); const int64 all = m_time.all(i); my_decimal time_d; my_decimal count_d; my_decimal all_d; my_decimal million_d; my_decimal temp_d; ulonglong2decimal(MILLION,&million_d); ulonglong2decimal(time, &temp_d); my_decimal_div(E_DEC_OK,&time_d,&temp_d,&million_d,SCALE); longlong2decimal(count,&count_d); longlong2decimal(all, &temp_d); my_decimal_div(E_DEC_OK,&all_d,&temp_d,&million_d,SCALE); fields[0]->store_decimal(&time_d); fields[1]->store_decimal(&count_d); fields[2]->store_decimal(&all_d); if (schema_table_store_record(thd, table)) { DBUG_RETURN(1); } } I want store some value to decimal type, than divide by MILLION: microsecond_count => convert to decimal => / 1000000 = result. But as result i get: SELECT * FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME; TIME COUNT TOTAL 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 1 11 4 10 8 13 100 0 0 1000 0 0 10000 0 0 ...................... Instead of wanted: SELECT * FROM INFORMATION_SCHEMA.QUERY_RESPONSE_TIME; TIME COUNT TOTAL 0.000001 0 0 0.00001 0 0 0.0001 1 0 0.001 0 0 0.01 1 0 0.1 0 0 1 11 4 10 8 13 100 0 0 1000 0 0 10000 0 0 ...................... 2) What i do incorrect? How fix it? Best regards, Oleg

2 1

Re: [Maria-discuss] Full Replacement of MySQL (innoDB, mysql Workbench, data, etc)
by Daniel Bartholomew 17 Aug '10

17 Aug '10

On Mon, 16 Aug 2010 16:25:00 -0000 Enrique Daniel <enridp(a)yahoo.com.ar> wrote: Enrique> Hi !! Hello! I'm CC'ing this message to the maria-discuss mailing list in case anyone else wants to comment. I recommend you join the list. It's a good resource. Enrique> I'm really new with MariaDB, I have discovered it yesterday at Enrique> really :S And I have not tested it yet, but it looks really Enrique> promising. Thanks! We've done lots of testing to make sure MariaDB works as seamlessly as possible for those moving from MySQL to MariaDB. As with any upgrade, I would definitely recommend making a backup and testing MariaDB on your end to ensure everything works with your applications and use-cases before putting it into production. Enrique> Anyway, there are a few things that are braking me to make the Enrique> change. I hope somebody can help me: Enrique> Enrique> 1) I'm using mySQL Workbench to design my DB, how can we use Enrique> it with MariaDB? (Aria, XtraDB engine, etc.) I haven't used MySQL Workbench much, but using it with MariaDB should be exactly the same as using it with MySQL. Enrique> 2) My tables ar InnoDB, but I was reading about XtraDB and it Enrique> looks much better, how can I make the change from innoDB to Enrique> XtraDB? if I have a SQL file, is enough changing ENGINE=INNODB Enrique> with ENGINE=XTRADB (or something like that). Enrique> I want to preserve my FK, with cascades, and comments. For compatibility purposes, XtraDB identifies itself to the server as InnoDB, so there's no need to change ENGINE= in any SQL files. Any existing InnoDB tables will start using XtraDB automatically after the upgrade. Enrique> 3) What happens if I have my DB with data and working with Enrique> MySQL and InnoDB right now? can I change to MariaDB (and Enrique> XtraDB) preserving all my scheme, tables, data, relations, Enrique> comments, indexes, etc? Yes. All of our testing indicates you can upgrade from MySQL to MariaDB and all of your schemas, tables, data, relations, comments, indexes, and so on will "just work" like they did with MySQL without you having to change anything. Of course, as with any upgrade, I would recommend testing on a non-production server before putting MariaDB into production. One last note. If you do find anything that doesn't work, please file a bug report: https://bugs.launchpad.net/maria/+filebug Thanks. -- Daniel Bartholomew Monty Program - http://askmonty.org

4 5

Re: [Maria-discuss] Full Replacement of MySQL (innoDB, mysql Workbench, data, etc)
by Henrik Ingo 16 Aug '10

16 Aug '10

I'm forwarding this to the mailing list since of all the places it was sent to, lp did not send it to the list... Please take care of this, nice MariaDB people: henrik On Mon, Aug 16, 2010 at 7:25 PM, Enrique Daniel <enridp(a)yahoo.com.ar> wrote: > Hi !! > I'm really new with MariaDB, I have discovered it yesterday at really :S > And I have not tested it yet, but it looks really promising. > > Anyway, there are a few things that are braking me to make the change. > I hope somebody can help me: > > 1) I'm using mySQL Workbench to design my DB, how can we use it with > MariaDB? (Aria, XtraDB engine, etc.) > > 2) My tables ar InnoDB, but I was reading about XtraDB and it looks much > better, how can I make the change from innoDB to XtraDB? if I have a SQL > file, is enough changing ENGINE=INNODB with ENGINE=XTRADB (or something > like that). > I want to preserve my FK, with cascades, and comments. > > 3) What happens if I have my DB with data and working with MySQL and > InnoDB right now? can I change to MariaDB (and XtraDB) preserving all my > scheme, tables, data, relations, comments, indexes, etc? > > Thanks !!! > Enrique. > -- > This message was sent from Launchpad by the user > Enrique Daniel (https://launchpad.net/~enridp) > using the "Contact this team" link on the Maria Discuss > team page to each member directly. > For more information see > https://help.launchpad.net/YourAccount/ContactingPeople > -- email: henrik.ingo(a)avoinelama.fi tel: +358-40-5697354 www: www.avoinelama.fi/~hingo book: www.openlife.cc

1 0

Re: [Maria-discuss] Locale settings and fractal number
by Oleg Tsarev 16 Aug '10

16 Aug '10

Hi, Sergey! I use string column, because i need fixed-point number (time column): 14_digit_to_second.6_digit_to_microsecond 123456.654321 as example. Big number, because i have not only "time" column and also "sum" column too. I didn't find any type what good for this, and i use string. Typically this columns use only by hand or in scripts, and don't used in any another queries. When i prepare output, i should print number and i don't know what the delimiter should i use. What the internal function should i call for get correct delimeter? Best regards, Oleg. 2010/8/16 Sergei Golubchik <serg(a)askmonty.org>: > Hi, Oleg! > > On Aug 15, Oleg Tsarev wrote: >> >> Hello all, >> >> I have feature >> http://www.percona.com/docs/wiki/patches:response_time_distribution >> Now i want respect locale settings, and use in "time" column >> locale-depended delimiter instead of current hardcoded ".". >> I investigate source code about that, and also bugzilla, >> documentation, but not found answer to my question - where this >> delimieter setup. >> >> What the "official" mysql policy? Use only "."? Or use native-locale? >> Or use some internal mysql function? >> Please, resolve my confuse. >> I want understand how this questions solved in mysql. > > As far as I understand, MySQL typically does not uses system locale > information for formatting numbers or dates. > > Anyway, you shouldn't care about locale - as you have two columns > of numbers, you need to have two numeric columns, say, DOUBLE and > BIGINT. > > Regards, > Sergei >

3 2

[Maria-discuss] Locale settings and fractal number
by Oleg Tsarev 15 Aug '10

15 Aug '10

Hello all, I have feature http://www.percona.com/docs/wiki/patches:response_time_distribution Now i want respect locale settings, and use in "time" column locale-depended delimiter instead of current hardcoded ".". I investigate source code about that, and also bugzilla, documentation, but not found answer to my question - where this delimieter setup. What the "official" mysql policy? Use only "."? Or use native-locale? Or use some internal mysql function? Please, resolve my confuse. I want understand how this questions solved in mysql. Thank you very much. --- Oleg Tsarev, Software Engineer, Percona Inc.

2 1

[Maria-discuss] Google docs now allows collaborative graphics and schemas
by Henrik Ingo 14 Aug '10

14 Aug '10

Hi I didn't try it yet, but Google docs just advertised the addition of a collaborative graphics app and schema drawing app. It's not open source of course, but it's better than nothing. Especially if they turn out to support ODF fileformats. henrik (This was a topic discussed at the devmeeting in Iceland.) -- email: henrik.ingo(a)avoinelama.fi tel: +358-40-5697354 www: www.avoinelama.fi/~hingo book: www.openlife.cc

1 0

[Maria-discuss] Wiki to Knowledgebase Move
by Daniel Bartholomew 13 Aug '10

13 Aug '10

All, I have started (and over the course of the next week I will continue) moving several pages from http://askmonty.org/wiki to http://kb.askmonty.org With the Knowledgebase now in beta it is time to move the content over. The procedure I plan on using for this is as follows: 1. Copy the content of a page from the wiki into the Knowledgebase. 2. Add a link to the top of the wiki page notifying of the move and giving a link to the new location of the page on the KB. 3. Add a redirect to the webserver config which automatically sends you to the KB page if you click on a link to the wiki page. I wanted to let you know about it now so that you are not surprised when you click on a link in the wiki and end up in the Knowledgebase. After most of the pages which are slated to be moved have been moved I will start deleting the pages from the wiki. The pages won't actually be gone (because of MediaWiki's undelete functionality) but having them officially deleted brings closure to the page and prevents it being accidentally viewed and/or edited. The pages slated to be moved include all of the ones in the "Manual:" namespace and several of the ones in the "MariaDB:" section. An easy way to think of it is that all documentation-type pages on the wiki are going to move to the Knowledgebase. Pages the developers use for planning releases (such as the 5.2 TODO page) will not move. Pages developers use to document new features will be moved when the developer indicates the page has become stable and ready to be used as documentation. In the future, some features will likely be documented first on the KB, but I'm sure there will always be some which begin life on the wiki. The redirects will stay in place indefinitely since keeping them around is easy and painless. The wiki will not go away, it is going to continue to be a site the MariaDB devs can use for notes, plans, and so on. The look will also change to better fit this mission. The corporate info, for example, has already been moved to http://montyprogram.com so the navigation links at the top of every page (About Us, Business, Partners, etc...) are no-longer necessary. Let me know if you have any questions or suggestions. Thanks. -- Daniel Bartholomew Monty Program - http://askmonty.org

1 0

[Maria-discuss] What is the log_bin and log_bin_index config for?
by Joshua Partogi 10 Aug '10

10 Aug '10

Hi all, Can anyone advise what is the log_bin and log_bin_index configuration in my.cnf for? When I enable both of this config and did and alter table on a table with PBXT engine, I encounter this error: MariaDB [bar]> alter table foo rename to tmp; ERROR 1598 (HY000): Binary logging not possible. Message: Statement-based format required for this statement, but not allowed by this combination of engines I am using MariaDB 5.1.47. Kind regards, Joshua. -- http://twitter.com/scrum8

2 1

[Maria-discuss] MySQL error code - forward compatible
by Oleg Tsarev 05 Aug '10

05 Aug '10

Dear MariaDB, Both Percona-Server/XtraDB and MariaDB experience problems concerning forward compatible error codes. 1) Both servers have a lot of features backported from mysql 5.5. Some features add new error (new error codes from MySQL 5.5). 2) Some Percona-Server/XtraDB and MariaDB features add new error code. In the first case we should save error code. For example, Percona has patch query_cache_totally_disable.patch (http://www.percona.com/docs/wiki/patches:query_cache_totally_disable) This patch adds error ER_QUERY_CACHE_DISABLED - error code number 1651 in mysql 5.5 (http://dev.mysql.com/doc/refman/5.5/en/error-messages-server.html#error_er_…) We must be consistent with error code numbers, because they may be used in scripts. After migrating PerconaServer/XtraDB and MariaDB to mysql 5.5, users might experience troubles because of this. In the second case we should add error code numbers, unique for our errors, as we cannot use any numbers from mysql 5.5. For example: http://www.percona.com/docs/wiki/patches:slave_type_conversions_error_on_tr… MySQL has a tool "comp_err" that generates 1) errmsg.sys files 2) header file include/mysqld_error.h 3) header file include/mysqld_ername.h from the file errmsg.txt To keep error numbers consistent, we should add some fictive errors to errmsg.txt, because comp_err assigns error code numbers sequentially, without gaps. I propose patch to comp_err (see attachment error_pad.patch). This patch allows usage of a new syntax, with prefix "PADD_", for example: PADD_QUERY_CACHE_DISABLED 1651 eng "ER_QUERY_CACHE_DISABLED padding to 1651 error" ER_QUERY_CACHE_DISABLED eng "Query cache is disabled; restart the server with query_cache_type=1 to enable it" comp_err with my patch padds empty intervals (from last error code number to 1651) by error message "ER_QUERY_CACHE_DISABLED padding to 1651 error", i.e. and ER_QUERY_CACHE_DISABLED now has error code 1651 (as desired). I propose to use this patch for Percona's and Maria's errors, for example: PADD_PERCONA_NEW_ERROR_CODE 4000 end "Padd empty space to error code number 4000 (Percona error codes)" ...some percona error codes... PADD_MARIA_DB_NEW_ERROR_CODE 5000 eng "Padd empty space to error code number 5000 (MariaDB error codes)" ...some maria error codes... Patch only adds prefix "PADD_" and padds error in sys files. All other mysql code (load*.sys files, my_error, etc) works as old one. Please, let me know what you think of it. Best regards, Oleg.

1 0

[Maria-discuss] Full text search in MariaDB
by Joshua Partogi 04 Aug '10

04 Aug '10

Hi all, We are currently using MariaDB in one of our products. One thing that we are wondering, does Maria engine currently supports Fulltext search like MyISAM? If currently not implemented yet, will there be any plan to implement fulltext support in MariaDB? Thank you very much in advance for your assistance. Kind regards, Joshua. -- http://twitter.com/scrum8

6 8

[Maria-discuss] New error code
by Олег Царев 03 Aug '10

03 Aug '10

Hi people, I solve trouble from previous letter by insert fictive errors. Now i have one more trouble - should add new error message to 5.1, bug i should respect forward compatible with mysql 5.5 What the error number get? Does mysql have reserved intervals for third-party patches? Thank you, Oleg.

2 1

[Maria-discuss] Error messages and Error codes (backport 5.5 => 5.1)
by Олег Царев 01 Aug '10

01 Aug '10

Hello all, I have troubles with backport some errors from 5.5 to 5.1 http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_… http://dev.mysql.com/doc/refman/5.5/en/error-messages-server.html#error_er_… Last error in mysql 5.1.49 - 1640. If i just add ER_QUERY_CACHE_DISABLED --- a/sql/share/errmsg.txt 2010-07-09 16:35:08.000000000 +0400 +++ b/sql/share/errmsg.txt 2010-07-31 20:41:47.244015659 +0400 @@ -6213,3 +6213,7 @@ ER_DEBUG_SYNC_HIT_LIMIT eng "debug sync point hit limit reached" ger "Debug Sync Point Hit Limit erreicht" + +ER_QUERY_CACHE_DISABLED + eng "Query cache is disabled; restart the server with query_cache_type=1 to enable it" + then error code of ER_DEBUG_SYNC_HIT_LIMIT is 1641 (instead of 1651 what i need). If i try: --- a/sql/share/errmsg.txt 2010-07-09 16:35:08.000000000 +0400 +++ b/sql/share/errmsg.txt 2010-07-31 20:41:47.244015659 +0400 @@ -6213,3 +6213,8 @@ ER_DEBUG_SYNC_HIT_LIMIT eng "debug sync point hit limit reached" ger "Debug Sync Point Hit Limit erreicht" + +start-error-number 1010 +ER_QUERY_CACHE_DISABLED + eng "Query cache is disabled; restart the server with query_cache_type=1 to enable it" + then mysql doesn't start with error in bootstrap.log like: "mysqld can't srart because errmsg.sys has only 642 errors, when last error number is ...." How can i backport error from mysql 5.5 to mysql 5.1 right? Now i solve trouble like: --- a/sql/share/errmsg.txt 2010-07-09 16:35:08.000000000 +0400 +++ b/sql/share/errmsg.txt 2010-07-31 20:41:47.244015659 +0400 @@ -6213,3 +6213,27 @@ ER_DEBUG_SYNC_HIT_LIMIT eng "debug sync point hit limit reached" ger "Debug Sync Point Hit Limit erreicht" + +ER_QUERY_CACHE_DISABLED_WRITE_SPACE_01 + eng "Fix error number for ER_QUERY_CACHE_DISABLED" +ER_QUERY_CACHE_DISABLED_WRITE_SPACE_02 + eng "Fix error number for ER_QUERY_CACHE_DISABLED" +ER_QUERY_CACHE_DISABLED_WRITE_SPACE_03 + eng "Fix error number for ER_QUERY_CACHE_DISABLED" +ER_QUERY_CACHE_DISABLED_WRITE_SPACE_04 + eng "Fix error number for ER_QUERY_CACHE_DISABLED" +ER_QUERY_CACHE_DISABLED_WRITE_SPACE_05 + eng "Fix error number for ER_QUERY_CACHE_DISABLED" +ER_QUERY_CACHE_DISABLED_WRITE_SPACE_06 + eng "Fix error number for ER_QUERY_CACHE_DISABLED" +ER_QUERY_CACHE_DISABLED_WRITE_SPACE_07 + eng "Fix error number for ER_QUERY_CACHE_DISABLED" +ER_QUERY_CACHE_DISABLED_WRITE_SPACE_08 + eng "Fix error number for ER_QUERY_CACHE_DISABLED" +ER_QUERY_CACHE_DISABLED_WRITE_SPACE_09 + eng "Fix error number for ER_QUERY_CACHE_DISABLED" +ER_QUERY_CACHE_DISABLED_WRITE_SPACE_10 + eng "Fix error number for ER_QUERY_CACHE_DISABLED" +ER_QUERY_CACHE_DISABLED + eng "Query cache is disabled; restart the server with query_cache_type=1 to enable it" + But this is ugly hack. What do you think about my trouble and ways for solve? Best regards, Oleg.

2 1

[Maria-discuss] Possible CVE from upstream
by Brian Evans 29 Jul '10

29 Jul '10

This seems to affect the released versions of MariaDB as well since they are based on 5.1.47 upstream as far as I can tell. CVE-2010-2008 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-2008) MySQL before 5.1.48 allows remote authenticated users with alter database privileges to cause a denial of service (server crash and database loss) via an ALTER DATABASE command with a #mysql50# string followed by a . (dot), .. (dot dot), ../ (dot dot slash) or similar sequence, and an UPGRADE DATA DIRECTORY NAME command, which causes MySQL to move certain directories to the server data directory.

1 0

[Maria-discuss] where are the buildbot results for valgrind and the InnoDB plugin?
by MARK CALLAGHAN 25 Jul '10

25 Jul '10

As described in http://mysqlha.blogspot.com/2010/07/building-mariadb-with-innodb-plugin.html I did some of the QA checks that I do for any new code that I might use. I have yet to find buildbot results for valgrind and the InnoDB plugin or XtraDB. Are they not run for buildbot? -- Mark Callaghan mdcallag(a)gmail.com

2 5

[Maria-discuss] (no subject)
by Justin Swanhart 16 Jun '10

16 Jun '10

http://wafejqh.wifethen.ru -- -- Justin Swanhart, Consultant, Percona Inc. Bay Area, USA (PDT, GMT -7) +1 888 401 3401 | Justin x503 | 24x7 Help x911 Our Services: http://www.percona.com/services.html Our Blog: http://www.mysqlperformanceblog.com/

3 2

[Maria-discuss] OpenSQLCamp EU Call for Papers
by Henrik Ingo 31 May '10

31 May '10

Giuseppe Maxia wanted me to bring to your attention, that the Call for Papers for OpenSQLCamp EU is now open: http://opensqlcamp.org/Events/2010/Call_for_Participation "The European OpenSQLCamp 2010 will take place in parallel to the Free and Open Source Conference 2010 (FrOSCon) on Saturday 21st and Sunday 22nd August at the Fachhochschule Bonn-Rhein-Sieg in St. Augustin, Germany. St. Augustin is located close to Bonn and Cologne. " henrik -- Henrik Ingo Project Manager and COO, Monty Program Ab hingo(a)askmonty.org, skype:henrik.ingo, +358405697354 http://askmonty.org/wiki/index.php/About_Us What's up with MariaDB? http://askmonty.org/wiki/index.php/MariaDB

1 0

[Maria-discuss] Please help me clear this simple but critical issue [SELECT INTO OUTFILE LOCAL]
by Cool Guy 20 May '10

20 May '10

MySQL is awesome! I am currently involved in a major server migration and previously, our small database used to be hosted on the same server as the client. So we used to do this : SELECT * INTO OUTFILE .... LOAD DATA INFILE .... Now, we moved the database to a different server and SELECT * INTO OUTFILE .... no longer works, understandable - security reasons I believe. But, interestingly LOAD DATA INFILE .... can be changed to LOAD DATA LOCAL INFILE .... and bam, it works. I am not complaining nor am I expressing disgust towards MySQL. The alternative to that added 2 lines of extra code and a system call form a .sql script. All I wanted to know is why LOAD DATA LOCAL INFILE works and why is there no such thing as SELECT INTO OUTFILE LOCAL? I did my homework, couldn't find a direct answer to my questions above. I couldn't find a feature request @ MySQL either. If someone can clear that up, that had be awesome! I am planning on suggesting MariaDB to our company cos' it is not under Oracle's admin. Does MariaDB already have this "SELECT INTO OUTFILE LOCAL .." feature implemented or is it in the wishlist/to-do list? Thank you, Kiran

3 14

[Maria-discuss] Someone from MariaDB to talk at ODTUG conference?
by Henrik Ingo 11 May '10

11 May '10

Hi all I just had a talk with Sheeri about an upcoming Oracle Developer Tools User Group conference in June in Washington. There will be a 1 day MySQL track on Sunday, plus possibly some other MySQL talks: http://www.odtugkaleidoscope.com/agenda.html Sheeri was asking if someone from Monty Program (or, imho any MariaDB activist) wanted to present. Things to note: - The conference is application developer oriented, so things like optimizer internals or tuning InnoDB buffer size is not interesting. - We don't want to talk about MariaDB per se. We don't want to introduce this crowd to the reality of there being so many MySQL forks. The previous points pretty much rule out everything we presented at the MySQL conference :-) Good topics could be: - Efficient and inefficient SQL queries in MySQL - UDF tutorial and examples The first suggestion is imho good. These Oracle experts need to learn to avoid certain things like most subqueries, and how to work around that. But on the other hand this is a natural topic for someone from us to present, since we could then also mention that correlated subqueries will work creat in MariaDB 5.3, which may even be beta by this point? The second suggestion is an example of something that would be considered very technical topic in this conference. Now the question is who to send there? This is not significant enough that someone from Europe would fly in - heh, most of us would probably not volunteer themselves at this point :-) In US I see Bryan or Daniel as candidates for this, Igor possibly for the UDF kind of talk more than the app developer talk. And, it needn't be a Monty Program employee, let me know if you're interested. Colin, will you pick this up from here? henrik -- email: henrik.ingo(a)avoinelama.fi tel: +358-40-5697354 www: www.avoinelama.fi/~hingo book: www.openlife.cc

1 1