- docs - lists.mariadb.org

Re: [Maria-docs] [Maria-discuss] transactions and UNLOCK TABLES
by Roberto Spadim 23 Sep '14

23 Sep '14

this don't work too: LOCK TABLE t WRITE; BEGIN; SELECT @@in_transaction; (return 1) UNLOCK TABLES; SELECT @@in_transaction; (return 1) maybe a wrong documentation 'bug'

1 1

[Maria-docs] query cache at askmonty kb
by Roberto Spadim 22 Sep '14

22 Sep '14

Hi guys first, thanks greenman to review query cache article well i have some others doubts at query cache that i think should/could be better explained 1) Limitations - The query cache needs to be disabled in order to use OQGRAPH <https://mariadb.com/kb/en/oqgraph/> and, in older versions, Galera <https://mariadb.com/kb/en/galera/>. - The query cache is not used by the Spider <https://mariadb.com/kb/en/spider/> storage engine (amongst others). why qc must be disabled with oqgraph? what's the possible problems without disabling it? maybe examples are wellcome, since reading oqgraph information we only have: Installing See Installing OQGRAPH <https://mariadb.com/kb/en/installing-oqgraph/>. Note that the query cache <https://mariadb.com/kb/en/query-cache/> needs to be disabled for OQGRAPH to function correctly. Spider have some sql_cache/sql_no_cache features, maybe should be nice a feature table about what engine support and how it support 2) include something related to query cache lock problems 2.1) write content lock while inserting new queries 2.2) global lock "quering" query cache before query execution 2.3) maybe we could include some benchmarks since today we have only the "it's a feature that must be disabled", but when use a read intensive database (like a wordpress or something like it) it could be enabled 2.4) maybe some explain about good pratices with query cache and without query cache i think that's all =) thanks again -- Roberto Spadim

2 1

[Maria-docs] List affecting CVEs at mariadb.com
by Otto Kekäläinen 26 Aug '14

26 Aug '14

Hello Daniel (and others), The usual changelogs[1] and relese notes[2] don't seem to contain CVE identifiers, or even a separate section about fixed security issues For the downstream security teams if would be reassuring if the CVE information would be easily available. For example if the security teams follow the CVE news and they for example know or suspect that CVE-2014-4260 affects MariaDB, it would be nice to see if it is already fixed or what version it was fixed in, so downstream security teams can organize and prioritize their patching and release work. Do you have any suggestion how to address this? Should we maybe have a separate wiki page, e.g. https://mariadb.com/kb/en/mariadb/cve/ that would have a table of CVEs and MariaDB 5.5/10.0/Galera versions where they are fixed? Or should just each release notes include a subsection "Security" with these details? Something else? Of course we need to consider timing issues, e.g. a security issue fixed in MariaDB might get publicity and a CVE only later when Oracle releases it, and in those cases old release notes need to be upgraded to include the CVE identifiers. [1] https://mariadb.com/kb/en/mariadb-10013-changelog/ [2] https://mariadb.com/kb/en/mariadb-10013-release-notes/ (To be exact, googling for 'mariadb cve' does give one hit at mariadb.com in the 5.3.12 release notes)

3 3

[Maria-docs] MariaDB 10.0.13 Release Prep
by Daniel Bartholomew 11 Aug '14

11 Aug '14

I've begun the prep work for the MariaDB 10.0.13 release. Draft changelog and release notes are here: - https://mariadb.com/kb/en/mariadb-10013-release-notes/ - https://mariadb.com/kb/en/mariadb-10013-changelog/ A big thanks to those that have already contributed content! As always, please let me know ASAP if anything else needs to be added/changed/etc..., or jump in and do it yourself. Thanks! -- Daniel Bartholomew, MariaDB Release Manager MariaDB | http://mariadb.com

1 0

[Maria-docs] innodb-buffer-pool-instances confusion
by Daniel Bartholomew 07 Aug '14

07 Aug '14

I was chatting with some folks on IRC and someone pointed this out to me. On the "Upgrading From MariaDB 5.5 to MariaDB 10.0" page, it says that the new default value for innodb-buffer-pool-instances is '0': https://mariadb.com/kb/en/upgrading-from-mariadb-55-to-mariadb-100/ And when I run the following, it says the default is indeed '0': mysqld --no-defaults --verbose --help | grep innodb-buffer-pool-instances ... innodb-buffer-pool-instances 0 But when I'm in the client, I get the following: MariaDB [(none)]> select @@innodb_buffer_pool_instances; +--------------------------------+ | @@innodb_buffer_pool_instances | +--------------------------------+ | 8 | +--------------------------------+ So when innodb-buffer-pool-instances is set to '0', does that mean the actual value is dynamic or calculated in some way based on my other settings? Just trying to understand what's going on, and once I do, use it to update the XtraDB/InnoDB buffer-pool page (which doesn't appear to have been updated for 10.0). https://mariadb.com/kb/en/xtradbinnodb-buffer-pool/ Thanks! -- Daniel Bartholomew, MariaDB Release Manager MariaDB | http://mariadb.com

4 3

[Maria-docs] MariaDB 5.5.39 Release Prep
by Daniel Bartholomew 05 Aug '14

05 Aug '14

All, I've begun prep work on the MariaDB 5.5.39 release. Draft release notes and changelog are here: - https://mariadb.com/kb/en/mariadb-5539-changelog/ - https://mariadb.com/kb/en/mariadb-5539-release-notes/ Please add any necessary or notable items to the release notes ASAP. Current plan is to activate/announce the release on 5 Aug. Thanks! -- Daniel Bartholomew, MariaDB Release Manager MariaDB | http://mariadb.com

1 0

[Maria-docs] MariaDB 10.0.12 release prep
by Daniel Bartholomew 14 Jun '14

14 Jun '14

I've begun prep work for the MariaDB 10.0.12 release. Draft Release Notes and Changelog are here: - https://mariadb.com/kb/en/mariadb-10012-release-notes/ - https://mariadb.com/kb/en/mariadb-10012-changelog/ Please add/modify/etc... as needed. Current plan is to announce the release on Mon, 16 Jun 2014. Thanks! -- Daniel Bartholomew, MariaDB Release Manager MariaDB | http://mariadb.com

1 0

[Maria-docs] MariaDB 5.5.38 Release Prep
by Daniel Bartholomew 07 Jun '14

07 Jun '14

All, I've begun prep work on the MariaDB 5.5.38 release. Draft release notes and changelog are here: - https://mariadb.com/kb/en/mariadb-5538-release-notes/ - https://mariadb.com/kb/en/mariadb-5538-changelog/ Current plan is to activate and announce the release on Mon, 9 jun 2014. Thanks. -- Daniel Bartholomew, MariaDB Release Manager MariaDB | http://mariadb.com

1 0

Re: [Maria-docs] doubt about kill documentation
by Roberto Spadim 26 May '14

26 May '14

Hi Ian! i think you forgot the maria-docs mailist at CC, i included it again ----- yes, i think that's a job of some MDEV: https://mariadb.atlassian.net/browse/MDEV-5425 https://mariadb.atlassian.net/browse/MDEV-4007 https://mariadb.atlassian.net/browse/MDEV-4427 and from last one (that i reported), this was the last comment from monty: Michael Widenius<https://mariadb.atlassian.net/secure/ViewProfile.jspa?name=monty> added a comment - 2014-04-22 08:19 We already have one implementation of this task. We are just waiting for the sponsor to pay for it so that we can push it. i will ask at jira if we have news about it 2014-05-26 16:47 GMT-03:00 Ian Gilfillan <ian(a)mariadb.org>: > Thanks for picking that up. > > I'm not sure of the history, but the original version of the page you're > referring to: > https://mariadb.com/kb/en/how-to-limittimeout-queries/13101/ > details such a feature, which was scheduled for inclusion in MariaDB 5.5.29 > > That feature never seemed to make it, and the link you've picked up is > still a legacy of that. > > I'll remove the mention and wait for the feature to actually arrive ;) > > ian > > > On 26/05/2014 21:26, Roberto Spadim wrote: > > hi guys, i was reading about kill query id > > https://mariadb.com/kb/en/data-manipulation-kill-connection-query/ > > at this part: > "The timeouts generated by MAX_QUERY_TIME<https://mariadb.com/kb/en/how-to-limittimeout-queries/#max_query_time-varia…> > use KILL SOFT QUERY. > " > > when i click at MAX_QUERY_TIME, i open a new link to a page that doesn't > explain what is MAX_QUERY_TIME > > hehe maybe a broken link? or a feature not developed yet? > > > > -- Roberto Spadim SPAEmpresarial Eng. Automação e Controle

1 0

[Maria-docs] doubt about kill documentation
by Roberto Spadim 26 May '14

26 May '14

hi guys, i was reading about kill query id https://mariadb.com/kb/en/data-manipulation-kill-connection-query/ at this part: "The timeouts generated by MAX_QUERY_TIME<https://mariadb.com/kb/en/how-to-limittimeout-queries/#max_query_time-varia…> use KILL SOFT QUERY. " when i click at MAX_QUERY_TIME, i open a new link to a page that doesn't explain what is MAX_QUERY_TIME hehe maybe a broken link? or a feature not developed yet? thanks! -- Roberto Spadim SPAEmpresarial Eng. Automação e Controle

1 0