delta/mariadb-git.git, branch bb-10.5-MDEV-30438 github.com: MariaDB/server.git MDEV-30438 innodb.undo_truncate,4k fails when innodb-immediate-scrub-data-uncompressed is enabled 2023-01-20T11:18:43+00:00 Thirunarayanan Balathandayuthapani thiru@mariadb.com 2023-01-20T10:37:43+00:00 645b6c19767421378f702d2d8c795b00e3202d0c - InnoDB fails to clear the freed ranges during truncation of innodb undo log tablespace. During shutdown, InnoDB flushes the freed page ranges and throws the out of bound error. mtr_t::commit_shrink(): clear the freed ranges while doing undo tablespace truncation 
- InnoDB fails to clear the freed ranges during truncation of innodb
undo log tablespace. During shutdown, InnoDB flushes the freed page
ranges and throws the out of bound error.

mtr_t::commit_shrink(): clear the freed ranges while doing undo
tablespace truncation
Merge 10.4 into 10.5 2023-01-13T08:18:30+00:00 Marko Mäkelä marko.makela@mariadb.com 2023-01-13T08:18:30+00:00 73ecab3d26c055928673a2629f4513aa7008dbf0 






Merge 10.3 into 10.4
2023-01-13T07:28:25+00:00

Marko Mäkelä
marko.makela@mariadb.com

2023-01-13T07:28:25+00:00

71e8e4934db06c02db1b51716e9d4b3992505161












MDEV-30378 Versioned REPLACE succeeds with ON DELETE RESTRICT constraint
2023-01-12T18:51:48+00:00

Nikita Malyavin
nikitamalyavin@gmail.com

2023-01-11T15:57:44+00:00

7a98d232e42b66efc759d584b05214e91681c346

node->is_delete was incorrectly set to NO_DELETE for a set of operations.

In general we shouldn't rely on sql_command and look for more abstract ways
to control the behavior.

trg_event_map seems to be a suitable way. To mind replica nodes, it is ORed
with slave_fk_event_map, which stores trg_event_map when replica has
triggers disabled.





node->is_delete was incorrectly set to NO_DELETE for a set of operations.

In general we shouldn't rely on sql_command and look for more abstract ways
to control the behavior.

trg_event_map seems to be a suitable way. To mind replica nodes, it is ORed
with slave_fk_event_map, which stores trg_event_map when replica has
triggers disabled.







MDEV-19160 json_pretty() alias for json_detailed()
2023-01-12T17:51:42+00:00

Weijun-H
huangweijun1001@gmail.com

2023-01-08T08:43:02+00:00

12618cfb28cb2843dc74bb3a176dae76acdb698a












fixup for MDEV-19160
2023-01-12T14:41:19+00:00

Rucha Deodhar
rucha.deodhar@mariadb.com

2023-01-12T14:41:19+00:00

17920291a661d3d2b02a9261293caebc7158d38a












fix typos
2023-01-12T03:02:20+00:00

lilinjie
lilinjie@uniontech.com

2023-01-12T02:38:38+00:00

eb145e5ad7afa29f1d298452b80fcca36a6c3bbe

Signed-off-by: lilinjie <lilinjie@uniontech.com>





Signed-off-by: lilinjie <lilinjie@uniontech.com>







Fixed failing test main.func_json
2023-01-12T00:48:33+00:00

Monty
monty@mariadb.org

2023-01-12T00:48:33+00:00

c08dba7b2864913bbf6fc36307837498f7def44a












MDEV-30345 DML does not find rows it is supposed to
2023-01-11T18:15:26+00:00

Monty
monty@mariadb.org

2023-01-11T18:15:26+00:00

f3d8a546e7476ddec8386eacd5c58bf1c1519377

This only happens with 'timestamp_column IN (select ...)

The reason was a missing assignment in Item_cache_timestamp::cache_value()





This only happens with 'timestamp_column IN (select ...)

The reason was a missing assignment in Item_cache_timestamp::cache_value()







MDEV-25277: mysqlbinlog --verbose cannot read row events with compressed columns: Don't know how to handle column type: 140
2023-01-11T17:37:49+00:00

Brandon Nesterenko
brandon.nesterenko@mariadb.com

2021-06-03T17:24:34+00:00

b194c83b7bd2f4e861fdce041a9ea3de18f4d227

Problem:
=======
Mysqlbinlog cannot show the type of a compressed
column when two levels of verbosity is provided.

Solution:
========
Extend the log event printing logic to handle and
tag compressed types.

Behavioral Changes:
==================
  Old: When mysqlbinlog is called in verbose mode and
the database uses compressed columns, an error is
returned to the user.

  New: The output will append “ COMPRESSED” on the
type of compressed columns

Reviewed By
===========
Andrei Elkin <andrei.elkin@mariadb.com>





Problem:
=======
Mysqlbinlog cannot show the type of a compressed
column when two levels of verbosity is provided.

Solution:
========
Extend the log event printing logic to handle and
tag compressed types.

Behavioral Changes:
==================
  Old: When mysqlbinlog is called in verbose mode and
the database uses compressed columns, an error is
returned to the user.

  New: The output will append “ COMPRESSED” on the
type of compressed columns

Reviewed By
===========
Andrei Elkin <andrei.elkin@mariadb.com>