Update License Book for Server 5.6.51 release

Approved-by: Bjorn Munch <[email protected]>

BUG#32019842: WRITE_SET VECTOR HAS NO UPPER MEMORY LIMIT

When the option is active, each server transaction will collect write
sets for each row, allowing to identify what changes the transaction
made, important for replication parallelization in general and Group
Replication conflict detection.

This patch improves the handling of write set collection for each
transaction in 2 ways.

First is that write sets are discarded if their size grow above
binlog_transaction_dependency_history_size. As a consequence the
transaction will no longer be marked as concurrent with previous ones
even if they touch different data.

The second one is that components like Group Replication can set
memory limits for the collection of write sets. Components like GR are
dependent on write sets being present, so they will never be
discarded, but breaking this memory limit will cause transactions to
abort.

ReviewBoard: 25520
ReviewBoard: 25592
(cherry picked from commit 933cc1c3b1dcf175de5aef0b6e2a826435481af6)

BUG#32019842: WRITE_SET VECTOR HAS NO UPPER MEMORY LIMIT

When the option is active, each server transaction will collect write
sets for each row, allowing to identify what changes the transaction
made, important for replication parallelization in general and Group
Replication conflict detection.

This patch improves the handling of write set collection for each
transaction in 2 ways.

First is that write sets are discarded if their size grow above
binlog_transaction_dependency_history_size. As a consequence the
transaction will no longer be marked as concurrent with previous ones
even if they touch different data.

The second one is that components like Group Replication can set
memory limits for the collection of write sets. Components like GR are
dependent on write sets being present, so they will never be
discarded, but breaking this memory limit will cause transactions to
abort.

ReviewBoard: 25520
ReviewBoard: 25592

Bug#32210815 REMOVE "ALL RIGHTS RESERVED TEXT" REFERENCES FROM COPYRI…

…GHT HEADER IN USER VISIBLE TEXT

Patch for 5.7.

Change-Id: I6f9c504d9760afe63461b7a1f59df695f51f1c53
(cherry picked from commit 6fe04c9f3a1f781a98d9747f4c8e0448882e72c6)

Bug#32210815 REMOVE "ALL RIGHTS RESERVED TEXT" REFERENCES FROM COPYRI…

…GHT HEADER IN USER VISIBLE TEXT

Patch for 5.6.

Change-Id: Ib90027051452599559cbc50eff102dcbb1480fed
(cherry picked from commit 3e5eab8265f97c19c7fc77d1f186f7f3ce739f63)

Bug#32210815 REMOVE "ALL RIGHTS RESERVED TEXT" REFERENCES FROM COPYRI…

…GHT HEADER IN USER VISIBLE TEXT

Patch for 5.6.

Change-Id: Ib90027051452599559cbc50eff102dcbb1480fed
(cherry picked from commit 3e5eab8265f97c19c7fc77d1f186f7f3ce739f63)

Bug #31472704 : MYSQL CRASHES ON SOME QUERIES WITH SUBSELECTS

Description:
Fix an issue with SELECT query.

Change-Id: I90a256bf237f1ce7860b1b3cfb25813287036607

Bug #31472704 : MYSQL CRASHES ON SOME QUERIES WITH SUBSELECTS

Description:
Fix an issue with SELECT query.

Change-Id: I90a256bf237f1ce7860b1b3cfb25813287036607
(cherry picked from commit b3039dc34acc2544f5451b7d55ff239cc4c268a9)