maria:queue-v1

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

3ad829d... by Sachin Setiya on 2021-03-11

commit 5

4b4a020... by Sachin Setiya on 2021-01-01

There are some memory error (while freeing)

6169c07... by Sachin Setiya on 2020-12-30

new code

c132e22... by Sachin Setiya on 2020-12-29

Queue with support of objects

f2f3fdc... by Sachin Setiya on 2020-11-17

Queue working without any issue

92cb994... by Sachin Setiya on 2020-11-05

Queue , Gives deadlock sometimes

5065389... by Sachin Setiya on 2020-10-27

xyz 2

e327596... by Sachin <email address hidden> on 2020-10-24

Something works

b4fb15c... by Marko Mäkelä on 2020-10-05

MDEV-16664: Remove innodb_lock_schedule_algorithm

The setting innodb_lock_schedule_algorithm=VATS that was introduced
in MDEV-11039 (commit 021212b525e39d332cddd0b9f1656e2fa8044905)
causes conflicting exclusive locks to be incorrectly granted to
two transactions. Specifically, in lock_rec_insert_by_trx_age()
the predicate !lock_rec_has_to_wait_in_queue(in_lock) would hold even
though an active transaction is already holding an exclusive lock.
This was observed between two DELETE of the same clustered index record.
The HASH_DELETE invocation in lock_rec_enqueue_waiting() may be related.

Due to lack of progress in diagnosing the problem, we will remove the
option. The unsafe option was enabled by default between
commit 0c15d1a6ff0d18da946f050cfeac176387a76112 (MariaDB 10.2.3)
and the parent of
commit 1cc1d0429da14a041a6240c6fce17e0d31cad8e2 (MariaDB 10.2.17, 10.3.9),
and it was deprecated in
commit 295e2d500b31819422c97ad77beb6226b961c207 (MariaDB 10.2.34).

3b72b35... by Marko Mäkelä on 2020-09-24

Merge 10.5 into 10.6