- docs - lists.mariadb.org

[Maria-docs] MariaDB versus MySQL page
by Daniel Bartholomew 13 Jun '10

13 Jun '10

Community Team, I'm sending this email to you since this is a wiki page which is not pure documentation and it's a page I feel the community team should have the final say on, content-wise. I'm also CC'ing the docs team, since that's what I do. :) Anyway, one of the pages on the wiki that needs some serious updating is the MariaDB versus MySQL page: http://askmonty.org/wiki/MariaDB_versus_MySQL As it currently exists it is an (outdated) version of a Release Notes page (with some extra stuff). Is that what we want for this page? If so we (or I) will need to come up with a better process whereby it always gets updated for each new release. At the very least, the page outline needs an overhaul. A second option would be to make this page more generic and/or not-release-specific which would make it easier to keep up-to-date since it wouldn't necessarily need to be updated for each release. If we go the more generic route, what type of information should be on the page? This page is a good place to talk about philosophical differences between the two camps. We could also do something like have a table of differences between MariaDB and MySQL. I'm thinking of something like this: Storage Engines MariaDB MySQL FederatedX Y N OQGRAPH Y N PBXT Y N XtraDB/InnoDB Y Y MyISAM Y Y and so on... ...expanded of course to include all sorts of information, not just storage engines. There is also a third option: We could nuke it from orbit. It's a drastic solution, but if anyone feels we should do this, let me know. In closing: I'm interested in hearing what you (and others) think the future of this page should be. Thanks. -- Daniel Bartholomew Monty Program - http://askmonty.org

3 2

[Maria-docs] Updates to MariaDB page
by Daniel Bartholomew 12 Jun '10

12 Jun '10

All, I've made some updates to the MariaDB page on the wiki to improve it and remove outdated information. http://askmonty.org/wiki/MariaDB I'd like to now invite the community team to review it and make any additions or changes they feel are appropriate. Thanks. -- Daniel Bartholomew Monty Program - http://askmonty.org

1 0

[Maria-docs] MariaDB 5.2.1 Release Notes and Changelog
by Daniel Bartholomew 05 Jun '10

05 Jun '10

All, MariaDB 5.2.1 is getting closer to being released so I've started filling out the Release Notes and Changelog pages: http://askmonty.org/wiki/Manual:MariaDB_5.2.1_Release_Notes http://askmonty.org/wiki/Manual:MariaDB_5.2.1_Changelog On the documentation TODO list for this release is a page on the OQGraph storage engine for the manual. Any volunteers? :) (I'll get to it next week, but if someone wants to put something up right away I wouldn't object.) Thanks. -- Daniel Bartholomew Monty Program - http://askmonty.org

1 0

[Maria-docs] Mixing GPL licensed material into our documentation
by Henrik Ingo 04 Jun '10

04 Jun '10

On Wed, Jun 2, 2010 at 11:07 PM, Daniel Bartholomew <dbart(a)askmonty.org> wrote: > On 12/05/2010, at 9:12 PM, Paul McCullagh > <paul.mccullagh(a)primebase.org> wrote: > > Paul> You are free to copy any part of the primebase.org documentation > Paul> to askmonty.org. > Paul> > Paul> It is not stated, but in general our documentation is also GPL. I > Paul> will add this to our Web-site. > > Paul, > > Thank you for licensing the documentation under the GPL and letting us > use it! Hmm... this reminds me: We've decided to use a combo of GFDL and CC BY-SA for our documentation licenses. Copying in documentation that is GPL licensed is probably not possible, I'm sure the GPL is incompatible with at least CC BY-SA. I'm not even concerned of the PBXT docs, I'm sure Paul would be flexible. But I just realized we also use the MySQL help files, which surely are GPL and we haven't seen much signs of MySQL being active in relicensing their docs ;-) This raises the question whether we should actually use GPL only as the license for our manual? It is copyleft too, so a workable choice even if it is "awkward" for literary works. A key question would be how much will we lose (such as in man-days of effort) if we just take away the MySQL help files from the manual? henrik -- email: henrik.ingo(a)avoinelama.fi tel: +358-40-5697354 www: www.avoinelama.fi/~hingo book: www.openlife.cc

2 4

[Maria-docs] xtstat documentation for MariaDB
by Daniel Bartholomew 03 Jun '10

03 Jun '10

Copying in the relevant bits of previous emails and CC'ing Maria-Docs for archival purposes. On Wed, 12 May 2010 14:06:17 +0300 Michael Widenius <monty(a)askmonty.org> wrote: Paul> Paul McCullagh has proposed merging Paul> lp:~paul-mccullagh/maria/add-xtstat-util into lp:maria. Paul> Requested reviews: Maria-captains (maria-captains) Paul> Paul> This patch includes the PBXT monitoring utility: xtstat. Paul> xtstat is installed in the bin directory along with Paul> other mysql binaries. Paul> Paul> The utility is very useful when using PBXT, as it shows Paul> you exactly what is happening in the engine. Paul> Paul> More details are provided in the documentation: Paul> http://primebase.org/documentation/index.php#xtstat, and Paul> in my conference talk: Paul> http://www.primebase.org/download/pbxt-uc-2010.pdf. Monty> I am now working on this. Monty> Monty> Paul, do you mind if we copy some of the documentation to the Monty> MariaDB documentation at askmonty.org ? On 12/05/2010, at 9:12 PM, Paul McCullagh <paul.mccullagh(a)primebase.org> wrote: Paul> You are free to copy any part of the primebase.org documentation Paul> to askmonty.org. Paul> Paul> It is not stated, but in general our documentation is also GPL. I Paul> will add this to our Web-site. Paul, Thank you for licensing the documentation under the GPL and letting us use it! I've added the xtstat documentation to our online manual here: http://askmonty.org/wiki/Manual:Xtstat As it exists currently, the page is mostly just a copy of your documentation with some minor rewording in a couple places and some re-formatting. When I get a chance I plan to re-create some of the examples from your UC presentation using MariaDB and add them to the page. Of course, you are free to make any changes or additions you want as well. I also linked back to the documentation on the PrimeBase site and to your PBXT presentation from the UC. Thanks again! -- Daniel Bartholomew Monty Program - http://askmonty.org

2 1

Re: [Maria-docs] Upcoming MariaDB 5.1.47 release
by Kristian Nielsen 02 Jun '10

02 Jun '10

MariaDB 5.1.47 packages are now uploaded to hasky. I've also provided the packages to OurDelta, looks like we will get repositories for MariaDB working again for this release (yay!). - Kristian. Kristian Nielsen <knielsen(a)knielsen-hq.org> writes: > I've tagged the 5.1-release tree with mariadb-5.1.47 and started building > packages for MariaDB 5.1.47. > > The release should be out early next week as soon as Daniel has had time to > prepare release notes and mirrors have caought up with packages. > > Daniel: Some things for release notes that I remember, to supplement what you > obtain from bzr commit messages: > > - New XtraDB version (If you don't find the version number in bzr, ask me to > dig it up from my notes). > > - New PBXT version. > > - Fix dependency problem with Ubuntu 10.04 Lucid packages, and build against > full release (no longer alpha). > > - Fix Ubuntu issue when using libmyodbc with mariadb packages. > > Regards, Kristian.

2 2

[Maria-docs] [Kristian Nielsen] Upcoming MariaDB 5.1.47 release
by Kristian Nielsen 30 May '10

30 May '10

1 0

[Maria-docs] FYI - new MariaDB:Mirroring page on wiki
by Daniel Bartholomew 28 May '10

28 May '10

All, I've created a new MariaDB:Mirroring page on the wiki. It has generic instructions for those that want to volunteer to mirror MariaDB. http://askmonty.org/wiki/MariaDB:Mirroring Constructive corrections, clarifications, and comments are welcome. Thanks. -- Daniel Bartholomew Monty Program - http://askmonty.org

1 0

Re: [Maria-docs] [Maria-developers] Segmented Key Cache - About section
by Daniel Bartholomew 19 May '10

19 May '10

On Mon, 17 May 2010 11:14:15 -0700 Igor Babaev <igor(a)askmonty.org> wrote: Daniel> The original sentence from the worklog reads: Daniel> So threads compete for this lock even in the case when they Daniel> have acquired shared locks for the file and pages they want Daniel> read from are in the key cache buffers. Igor> Ok ,I will help with the reading of the original statement adding Igor> missing words: Igor> Igor> So threads compete for this lock even in the case when Igor> they have acquired shared locks for the file Igor> and Igor> the pages they want to read from are in the key cache buffers. Thanks for the clarification! -- Daniel Bartholomew Monty Program - http://askmonty.org

1 0

[Maria-docs] Segmented Key Cache - Syntax section
by Daniel Bartholomew 18 May '10

18 May '10

Hello everyone, Summarizing from my previous email: I'm working on the documentation for the Segmented Key Cache, one of the new features in MariaDB 5.2. My previous email was about the "About" section of the documentation. This email is about the "Syntax" section. For the syntax section, I see there is one new global variable defined for this feature and a new KEY_CACHES table in the information_schema database. Are there any other user-visible items which should be mentioned? Here is a first draft of the syntax section: ---------------------------------------------------------------------- == Segmented Key Cache Syntax == New global variable: key_cache_partitions, it sets the number of segments in a key cache. Valid values for this variable are whole numbers between 0 and 64. If the number of partitions is set to a number greater than 64 the number of partitions will be truncated to 64 and a warning will be issued. A value of '0' means the key cache is a regular (i.e. non-segmented) key cache. This is the default. Other global variables used when working with regular key caches also apply to segmented key caches: key_buffer_size, key_cache_age_threshold, key_cache_block_size, and key_cache_division_limit. See the MySQL manual for descriptions of these variables. http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html Statistics about the key cache can be found by looking at the KEY_CACHES table in the INFORMATION_SCHEMA database. Columns in this table are: * KEY_CACHE_NAME: The name of the key cache * PARTITIONS: total number of segments * PARTITION_NUMBER: segment number (set to NULL if a simple key cache) * FULL_SIZE: memory for cache buffers/auxiliary structures * BLOCK_SIZE: size of the blocks * USED_BLOCKS: number of currently used blocks * UNUSED_BLOCKS: number of currently unused blocks * DIRTY_BLOCKS: number of currently dirty blocks * READ_REQUESTS: number of read requests * READS: number of actual reads from files into buffers * WRITE_REQUESTS: number of write requests * WRITES: number of actual writes from buffers into files ---------------------------------------------------------------------- If there are any factual errors with the above, let me know. Improvements and suggestions are also welcome. Question for the developers: A key_cache_partitions value of '0' means the key cache will not be segmented, it will be a regular (or simple) key cache. A value of '1' means the key cache will be a segmented key cache with a single segment. Is there any benefit to having a "single-segment segmented key cache" compared to a regular "simple key cache" or are they practically the same thing? The key_cache_partitions variable also needs to be documented on the Server System Variables page (http://askmonty.org/wiki/Manual:Server_System_Variables) The entry will look something like this: ---------------------------------------------------------------------- * <code>key_cache_partitions</code> ** '''Description:''' The number of segments in a key cache. ** '''Commandline:''' <code>--key_cache_partitions=#</code> ** '''Scope:''' Global ** '''Dynamic:''' No ** '''Type:''' number ** '''Valid values:''' <code>0-64</code> ** '''Default value:''' <code>0</code> ''(non-segmented)'' * '''Introduced:''' MariaDB 5.2 ---------------------------------------------------------------------- Let me know if there is anything wrong with the above. My task now is to come up with some examples. I'll probably use the test cases for inspiration unless someone has an awesome segmented key cache example that they've been dying to share with me. :) Thanks. -- Daniel Bartholomew Monty Program - http://askmonty.org

3 3