1. 10 Sep, 2018 2 commits
  2. 09 Sep, 2018 2 commits
    • Sergey Vojtovich's avatar
      Fixed c++11 narrowing error · a0dfefb0
      Sergey Vojtovich authored
      sql/table.cc:8561:42: error: non-constant-expression cannot be narrowed
                                   from type 'uint' (aka 'unsigned int') to
                                   '__darwin_suseconds_t' (aka 'int') in
                                   initializer list [-Wc++11-narrowing]
        timeval end_time= {thd->query_start(), uint(thd->query_start_sec_part())};
                                               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      sql/table.cc:8561:42: note: insert an explicit cast to silence this issue
        timeval end_time= {thd->query_start(), uint(thd->query_start_sec_part())};
                                               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                               static_cast<__darwin_suseconds_t>( )
      a0dfefb0
    • Sergey Vojtovich's avatar
      Enable C++11 · d9613b75
      Sergey Vojtovich authored
      d9613b75
  3. 07 Sep, 2018 1 commit
    • Igor Babaev's avatar
      EV-16992 Assertion `table_ref->table || table_ref->view' failed in · 96572b7a
      Igor Babaev authored
                 Field_iterator_table_ref::set_field_iterator
      
      Several functions that processed different prepare statements missed
      the DT_INIT flag in last parameter of the open_normal_and_derived_tables()
      calls. It made context analysis of derived tables dependent on the order in
      which the derived tables were processed by mysql_handle_derived(). This
      order was induced by the order of SELECTs in all_select_list.
      In 10.4 the order of SELECTs in all_select_list became different and lack
      of the DT_INIT flags in some open_normal_and_derived_tables() call became
      critical as some derived tables were not identified as such.
      96572b7a
  4. 30 Aug, 2018 1 commit
    • Jacob Mathew's avatar
      MDEV-16889: Spider Crash mysqld got exception 0xc0000005 · f6694b62
      Jacob Mathew authored
      The SELECT with the INNER JOIN is executed with one of the two tables being
      optimized as a constant table, which is pre-read.  Spider nevertheless attempts
      to push down the join to the data node.  The crash occurs because the constant
      table is excluded from the optimized query that Spider attempts to push down.
      
      In order for Spider to be able to push down a join, the following conditions
      need to be met:
      - All of the tables involved in the join need to be included in the optimized
        query that Spider pushes down.  When any of the tables involved in the join
        is a constant table, it is excluded from the optimized query that Spider
        attempts to push down.
      - All fields involved in the query need to be members of tables included in the
        optimized query.
      
      I fixed the problem by preventing Spider from pushing down queries that include
      a field that is not a member of a table included in the optimized query.  This
      solution fixes the reported problem and also fixes other potential problems.
      
      Author:
        Jacob Mathew.
      
      Reviewer:
        Kentoku Shiba.
      
      Cherry-Picked:
        Commit 4885baf6 on branch bb-10.3-MDEV-16889
      f6694b62
  5. 28 Aug, 2018 3 commits
    • Jacob Mathew's avatar
      MDEV-16250: Spider system tables are MyISAM and needs repair after a crash · 6ccd7d2d
      Jacob Mathew authored
      During a server restart that follows a server crash, there may be error
      messages that indicate that certain system tables are marked as crashed and
      may be corrupted.  Upon checking the system tables that are marked as crashed,
      it may be found that there is no corruption that needs repair.  However, the
      error messages that are issued imply that the user needs to nevertheless
      manually repair the system tables that were marked as crashed.  These issues
      have been moved to a separate bug MDEV-17068.
      
      MDEV-16250 addresses the work to make the Spider system tables crash safe.
      This work involves the following changes in 10.4:
      - Changes to the install_spider.sql script to change the storage engine for
        the Spider system tables to Aria.  This is implemented in such a way as to
        allow the script to be run repeatedly without any harm or errors.
      - Changes to the init_spider.inc script that is run during initialization of
        every test in the Spider test suites.  This script now uses the Aria
        storage engine for the Spider system tables in MariaDB Server 10.4 and
        later releases.
      - Added a test to the Spider test suite to display the storage engine of each
        Spider system table, to verify that the correct storage engine is used.
      
      Author:
        Jacob Mathew.
      
      Reviewer:
        Kentoku Shiba.
      
      Merged:
        Commit 73fac2a5 from branch bb-10.4-MDEV-16250
      6ccd7d2d
    • Monty's avatar
      MDEV-17068 mysql system table is marked as crashed and should be repaired... · 8cc53ade
      Monty authored
      MDEV-17068 mysql system table is marked as crashed and should be repaired after the server crashes or is killed
      
      - Changed ERROR to WARNING for MyISAM/Aria message
        that are warnings in the check utilities.
        This affects for example "client is using or
        hasn't closed the table properly".
      - Print "Table is fixed" if check succeded in
        fixing the table.
      8cc53ade
    • Monty's avatar
      Updated company name in Aria plugin definition · f451fd8c
      Monty authored
      f451fd8c
  6. 27 Aug, 2018 1 commit
    • Jacob Mathew's avatar
      MDEV-16250: Spider system tables are MyISAM and needs repair after a crash · 73fac2a5
      Jacob Mathew authored
      During a server restart that follows a server crash, there may be error
      messages that indicate that certain system tables are marked as crashed and
      may be corrupted.  Upon checking the system tables that are marked as crashed,
      it may be found that there is no corruption that needs repair.  However, the
      error messages that are issued imply that the user needs to nevertheless
      manually repair the system tables that were marked as crashed.  These issues
      have been moved to a separate bug MDEV-17068.
      
      MDEV-16250 addresses the work to make the Spider system tables crash safe.
      This work involves the following changes in 10.4:
      - Changes to the install_spider.sql script to change the storage engine for
        the Spider system tables to Aria.  This is implemented in such a way as to
        allow the script to be run repeatedly without any harm or errors.
      - Changes to the init_spider.inc script that is run during initialization of
        every test in the Spider test suites.  This script now uses the Aria
        storage engine for the Spider system tables in MariaDB Server 10.4 and
        later releases.
      - Added a test to the Spider test suite to display the storage engine of each
        Spider system table, to verify that the correct storage engine is used.
      
      Author:
        Jacob Mathew.
      
      Reviewer:
        Kentoku Shiba.
      73fac2a5
  7. 24 Aug, 2018 1 commit
  8. 20 Aug, 2018 3 commits
  9. 18 Aug, 2018 1 commit
  10. 17 Aug, 2018 2 commits
    • Varun Gupta's avatar
      Fixed ASAN failure for the test main.func_misc. · bf1c53e9
      Varun Gupta authored
      For Item name_const , we should never do typecast it to Item_field because we
      always expect it to be a constant value.
      So instead of checking the type() its better to introduce a function in the
      Item class get_item_field, which would return the item_field object for the item
      which have type of FIELD_ITEM
      bf1c53e9
    • Monty's avatar
      MDEV-16986 Unitialized mutex, SIGSEGV and assorted assertion failures in Aria code · 3faed09d
      Monty authored
      This was introduced by two pointers I added to TRN
      as part of MDEV-16421 Make system tables crash safe
      
      - Added code to ensure that trn_prev is not pointing
        to wrong object
      - A lot of new asserts and more code comments
      - Simplified code in _ma_trnman_end_trans_hook()
        - New back link allowed me to remove a loop
      3faed09d
  11. 16 Aug, 2018 10 commits
  12. 15 Aug, 2018 4 commits
  13. 14 Aug, 2018 7 commits
    • Marko Mäkelä's avatar
      MDEV-15872 Crash in online ALTER TABLE...ADD PRIMARY KEY after instant ADD COLUMN...NULL · 021652ba
      Marko Mäkelä authored
      row_log_table_get_pk_col(): Replace a condition that was inadvertently
      removed in MDEV-16365. PRIMARY KEY columns are never allowed to be NULL,
      and failure to enforce the constraint caused a null pointer to be
      dereferenced in mem_heap_dup().
      021652ba
    • Daniel Bartholomew's avatar
      bump the VERSION · 964ad0c4
      Daniel Bartholomew authored
      964ad0c4
    • Vladislav Vaintroub's avatar
    • Michael Widenius's avatar
      MDEV-16421 Make system tables crash safe · d6d63f48
      Michael Widenius authored
      Make all system tables in mysql directory of type
      engine=Aria
      
      Privilege tables are using transactional=1
      Statistical tables are using transactional=0, to allow them
      to be quickly updated with low overhead.
      Help tables are also using transactional=0 as these are only
      updated at init time.
      
      Other changes:
      - Aria store engine is now a required engine
      - Update comment for Aria tables to reflect their new usage
      - Fixed that _ma_reset_trn_for_table() removes unlocked table
        from transaction table list. This was needed to allow one
        to lock and unlock system tables separately from other
        tables, for example when reading a procedure from mysql.proc
      - Don't give a warning when using transactional=1 for engines
        that is using transactions. This is both logical and also
        to avoid warnings/errors when doing an alter of a privilege
        table to InnoDB.
      - Don't abort on warnings from ALTER TABLE for changes that
        would be accepted by CREATE TABLE.
      - New created Aria transactional tables are marked as not movable
        (as they include create_rename_lsn).
      - bootstrap.test was changed to kill orignal server, as one
        can't anymore have two servers started at same time on same
        data directory and data files.
      - Disable maria.small_blocksize as one can't anymore change
        aria block size after system tables are created.
      - Speed up creation of help tables by using lock tables.
      - wsrep_sst_resync now also copies Aria redo logs.
      d6d63f48
    • Monty's avatar
      Fixed some source comments and help texts · 0e0f1092
      Monty authored
      0e0f1092
    • Monty's avatar
      Remove warning from perfschema.bad_option_# tests · 5e1bbf66
      Monty authored
      5e1bbf66
    • Michael Widenius's avatar
      Updated wrong result files · cf7b48ff
      Michael Widenius authored
      cf7b48ff
  14. 13 Aug, 2018 2 commits