mariadb

Tree: 9bc874a594

Author	SHA1	Message	Date
Marko Mäkelä	9bc874a594	MDEV-23497 Make ROW_FORMAT=COMPRESSED read-only by default Let us introduce the parameter innodb_read_only_compressed that is ON by default, making any ROW_FORMAT=COMPRESSED tables read-only. I developed the ROW_FORMAT=COMPRESSED format based on Heikki Tuuri's rough design between 2005 and 2008. It might have been a good idea back then, but no proper benchmarks were ever run to validate the design or the implementation. The format has been more or less obsolete for years. It limits innodb_page_size to 16384 bytes (the default), and instant ALTER TABLE is not supported. This is the first step towards deprecating and removing write support for ROW_FORMAT=COMPRESSED tables.	5 years ago
Eugene Kosov	5ebef42238	MDEV-19292 "Row size too large" error when creating table with lots columns when row format is DYNAMIC or COMPRESSED Basic idea of the patch: disallow creating tables which allow to create rows which are too big to insert. In other words, if user created a table user should never see an errors like 'can not insert row as it is too big for current page size'. SET innodb_strict_mode=OFF; will allow to create very long tables and only a warning will be issued. dict_table_t::get_overflow_field_local_len(): this function lets know a maximum local field len for overflow fields for every file and row format. innobase_check_column_length(): improve name to too_big_key_part_length() and reuse in a different part of code. create_table_info_t::prepare_create_table(): add check for maximum allowed key part length to keep ALGORITHM=COPY behavior similar to ALGORITHM=INPLACE behavior. Affected test is innodb.strict_mode Rename dict_index_too_big_for_tree() to dict_index_t::rec_potentially_too_big(): copy overflow-related size computation from dtuple_convert_big_rec(). A lot of tests was changed because of that. I wonder whether users will complain about it? Test innodb.max_record_size tests dict_index_t::rec_potentially_too_big() for different row formats and page sizes.	6 years ago
Marko Mäkelä	2af28a363c	MDEV-11782: Redefine the innodb_encrypt_log format Write only one encryption key to the checkpoint page. Use 4 bytes of nonce. Encrypt more of each redo log block, only skipping the 4-byte field LOG_BLOCK_HDR_NO which the initialization vector is derived from. Issue notes, not warning messages for rewriting the redo log files. recv_recovery_from_checkpoint_finish(): Do not generate any redo log, because we must avoid that before rewriting the redo log files, or otherwise a crash during a redo log rewrite (removing or adding encryption) may end up making the database unrecoverable. Instead, do these tasks in innobase_start_or_create_for_mysql(). Issue a firm "Missing MLOG_CHECKPOINT" error message. Remove some unreachable code and duplicated error messages for log corruption. LOG_HEADER_FORMAT_ENCRYPTED: A flag for identifying an encrypted redo log format. log_group_t::is_encrypted(), log_t::is_encrypted(): Determine if the redo log is in encrypted format. recv_find_max_checkpoint(): Interpret LOG_HEADER_FORMAT_ENCRYPTED. srv_prepare_to_delete_redo_log_files(): Display NOTE messages about adding or removing encryption. Do not issue warnings for redo log resizing any more. innobase_start_or_create_for_mysql(): Rebuild the redo logs also when the encryption changes. innodb_log_checksums_func_update(): Always use the CRC-32C checksum if innodb_encrypt_log. If needed, issue a warning that innodb_encrypt_log implies innodb_log_checksums. log_group_write_buf(): Compute the checksum on the encrypted block contents, so that transmission errors or incomplete blocks can be detected without decrypting. Rewrite most of the redo log encryption code. Only remember one encryption key at a time (but remember up to 5 when upgrading from the MariaDB 10.1 format.)	9 years ago
Marko Mäkelä	08413254b7	Remove references to innodb_file_format. innodb_file_format=Barracuda is the default in MariaDB 10.2. Do not set it, because the option will be removed in MariaDB 10.3. Also, do not set innodb_file_per_table=1 because it is the default. Note that MDEV-11828 should fix the test innodb.innodb-64k already in 10.1.	9 years ago
Jan Lindström	25f8738112	MDEV-9040: 10.1.8 fails after upgrade from 10.0.21 Analysis: Lengths which are not UNIV_SQL_NULL, but bigger than the following number indicate that a field contains a reference to an externally stored part of the field in the tablespace. The length field then contains the sum of the following flag and the locally stored len. This was incorrectly set to define UNIV_EXTERN_STORAGE_FIELD (UNIV_SQL_NULL - UNIV_PAGE_SIZE_MAX) When it should be define UNIV_EXTERN_STORAGE_FIELD (UNIV_SQL_NULL - UNIV_PAGE_SIZE_DEF) Additionally, we need to disable support for > 16K page size for row compressed tables because a compressed page directory entry reserves 14 bits for the start offset and 2 bits for flags. This limits the uncompressed page size to 16k. To support larger pages page directory entry needs to be larger.	10 years ago
Jan Lindström	9d399c9f35	MDEV-6075: Allow > 16K pages on InnoDB This patch allows up to 64K pages for tables with DYNAMIC, COMPACT and REDUNDANT row types. Tables with COMPRESSED row type allows still only <= 16K page size. Note that single row size must be still <= 16K and max key length is not affected.	12 years ago

8 Commits (9bc874a594edbc0e124131d0ff30b44f5fade52d)