maria-developers team mailing list archive

Thread
Date

Re: 1e9ea675a18: MDEV-21282 Assertion 'mariadb_table' failed in gcol.innodb_virtual_debug_purge

To: Thirunarayanan Balathandayuthapani <thiru@xxxxxxxxxxx>
From: Sergei Golubchik <serg@xxxxxxxxxxx>
Date: Wed, 3 Jun 2020 17:02:33 +0200
Cc: maria-developers@xxxxxxxxxxxxxxxxxxx
In-reply-to: <3kO5j_EIcLB.A.VBE.Og71eB@pweza>

Hi, Thirunarayanan!

Sure, it's purely InnoDB functionality. If you say that purge thread
already hold MDL for the table, then open_purge_table() doesn't need to.

Ok to push as you see fit.

On Jun 03, Thirunarayanan Balathandayuthapani wrote:
> revision-id: 1e9ea675a18 (mariadb-10.5.2-304-g1e9ea675a18)
> parent(s): f22093ad392
> author: Thirunarayanan Balathandayuthapani <thiru@xxxxxxxxxxx>
> committer: Thirunarayanan Balathandayuthapani <thiru@xxxxxxxxxxx>
> timestamp: 2020-06-01 18:02:17 +0530
> message:
> 
> MDEV-21282 Assertion 'mariadb_table' failed in gcol.innodb_virtual_debug_purge
> 
> - commit ea37b144094a0c2ebfc6774047fd473c1b2a8658 (MDEV-16678) caused
> a regression. when purge thread tries to open the table for virtual
> column computation, there is no need to acquire MDL for the table.
> Because purge thread already hold MDL for the table

Regards,
Sergei
VP of MariaDB Server Engineering
and security@xxxxxxxxxxx