August 2010 - discuss - lists.mariadb.org

[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