Re: [Maria-developers] Doublewrite block number in XtraDB

2017-02-09 Thread Marko Mäkelä
Hank, Thank you for letting me know about the innodb_doublewrite_file parameter. I understand that it existed in Percona XtraDB for MySQL 5.5 but was not ported to their MySQL 5.6 based XtraDB. The MariaDB documentation at https://mariadb.com/kb/en/mariadb/xtradbinnodb-doublewrite-buffer/ agrees t

Re: [Maria-developers] Doublewrite block number in XtraDB

2017-02-09 Thread Hank Lyu
Hi, In MariaDB Server 10.2, is the default storage engine InnoDB instead of XtraDB? The feature MDEV-11659 Move the InnoDB doublewrite buffer to flat files , I remember that the similarly feature was implement in XtraDB before MariaDB 10.0 and it can se

Re: [Maria-developers] [Commits] 15fde78: MDEV-10731: Wrong NULL match results in "Subquery returns more than 1 row" (error code 1242)

2017-02-09 Thread Sergey Petrunia
Hi Varun, On Thu, Feb 09, 2017 at 10:37:17PM +0530, Varun wrote: > revision-id: 15fde78ce812c8db91340936941b986fb28ce1ad > (mariadb-10.1.20-82-g15fde78) > parent(s): 99b2de92c6214ddd73eba35c935f490eedf87a26 > author: Varun Gupta > committer: Varun Gupta > timestamp: 2017-02-09 22:36:03 +0530 > me

Re: [Maria-developers] bb-10.2-compatibility

2017-02-09 Thread jerome brauge
Hello Alexander, Thanks for these news and sub-task ! Yes, it commit top-level transaction (as long as you are not in an autonomous transaction). The main difference between Mariadb and Oracle transaction is that Oracle implicitly starts a transaction when the first SQL statement (which need to

Re: [Maria-developers] bb-10.2-compatibility

2017-02-09 Thread Alexander Barkov
Hello Jerome, On 02/09/2017 04:44 PM, Alexander Barkov wrote: > Hello Jerome, > > > On 02/09/2017 02:54 PM, jerome brauge wrote: >> Hello, >> >> I come back with a question on functions. >> >> On Oracle, there is only one difference between a function and a stored >> procedure : the return cod

Re: [Maria-developers] bb-10.2-compatibility

2017-02-09 Thread Alexander Barkov
Hello Jerome, On 02/09/2017 02:54 PM, jerome brauge wrote: > Hello, > > I come back with a question on functions. > > On Oracle, there is only one difference between a function and a stored > procedure : the return code. > > On Mariadb, stored functions are more limited : > - Recursive stor

Re: [Maria-developers] MDEV-10697 - bb-10.2-compatibility

2017-02-09 Thread Alexander Barkov
Hello Jerome, The last version looks very good. Thanks!. Note, I haven't made a detailed review for sp-goto.test yet. Will reply about tests in a separate letter. On 02/08/2017 06:31 PM, jerome brauge wrote: > Hi Alexander, > I'm sorry to waste your time for formatting and/or coding style issue

Re: [Maria-developers] [Commits] cb918231a25: MDEV-11582 InnoDB: Failing assertion: !((field)->vcol_info && !(field)->stored_in_db())

2017-02-09 Thread Alexander Barkov
Hello Sergei, The patch looks fine. I suggest one improvement. Currently SERIAL can have various redundant, ignored, non-applicable attributes, e.g.: CREATE TABLE t1 (a SERIAL NULL); CREATE TABLE t1 (a SERIAL AUTO_INCREMENT); CREATE TABLE t1 (a SERIAL SERIAL DEFAULT VALUE); CREATE OR REPLACE TAB

[Maria-developers] bb-10.2-compatibility

2017-02-09 Thread jerome brauge
Hello, I come back with a question on functions. On Oracle, there is only one difference between a function and a stored procedure : the return code. On Mariadb, stored functions are more limited : - Recursive stored functions are not allowed - Explicit or implicit commit is not allowed in s

[Maria-developers] Blackhole, Archive and others only as loadable plugins in 10.1 - intentional change?

2017-02-09 Thread Hartmut Holzgraefe
In MariaDB 10.1 binary packages several storage engines, e.g BLACKHOLE and ARCHIVE, are no longer compiled in by default but only come as loadable plugins that need to be loaded into the server explicitly. This is mentioned on the knowledge base pages for these engines, e.g. https://mariadb.com/kb

Re: [Maria-developers] Doublewrite block number in XtraDB

2017-02-09 Thread Marko Mäkelä
Hi, I think that the doublewrite buffer would become more flexible and perform better if it was moved out of the InnoDB system tablespace. Then we could use any number of pages and not be limited to 128 pages. I filed MDEV-11659 Move the InnoDB doublewrite buffer to flat files