7 Commits

Author	SHA1	Message	Date
sjaakola	d5a15f04f4	MDEV-24978 crash with transaction on table with no PK and long fulltext column ... If a table has no unique indexes, write set key information will be collected on all columns in the table. The write set key information has space only for max 3500 bytes for individual column, and if a varchar colummn of such non-primary key table is longer than this limit, currently a crash follows. The fix in this commit, is to truncate key values extracted from such long varhar columns to max 3500 bytes. This may potentially lead to false positive certification failures for transactions, which operate on separate cluster nodes, and update/insert/delete table rows, which differ only in the part of such long columns after 3500 bytes border. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>	2021-09-30 11:19:34 +03:00
Jan Lindström	1a62c87897	Remove test from galera_fulltext until MDEV-24978 is fixed.	2021-09-27 08:25:22 +03:00
Jan Lindström	47ba552304	Revert "MDEV-24978 : SIGABRT in __libc_message" ... This reverts commit 30dea4599e.	2021-09-24 09:47:31 +03:00
Jan Lindström	f55477060c	MDEV-26518 ; Galera incorrectly handles primary or unique keys with any multi-byte character set ... We need to set temporary buffer large enough to fit also multi-byte characters.	2021-09-02 07:32:19 +03:00
Jan Lindström	30dea4599e	MDEV-24978 : SIGABRT in __libc_message ... Keyvalue can be longer than REC_VERSION_56_MAX_INDEX_COL_LEN and this leads out-of-array reference. Use dynamic memory allocation using actual max length of key value.	2021-03-15 11:56:42 +02:00
Philip Stoev	f8b724db28	Galera MTR Tests: Enable the use of --parallel for port-intensive Galera tests by additionally specifying --port-group-size=50	2015-09-09 20:56:41 -04:00
Nirbhay Choubey	3331d4e07e	Merge galera tests from github.com/codership/mysql-wsrep	2015-05-08 17:43:57 -04:00