mariadb/innodb-spatial-index.opt at c764bc0a78e9359fa208e074bd327f7a852c7cb7 - mariadb - GitFox

database/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-11-03 14:33:32 +03:00

Files

Jan Lindström 7b27465e10 MDEV-11974: MariaDB 10.2 encryption does not support spatial indexes

Encryption stores used key_version to
FIL_PAGE_FILE_FLUSH_LSN_OR_KEY_VERSION (offset 26)
field. Spatial indexes store RTREE Split Sequence Number
(FIL_RTREE_SPLIT_SEQ_NUM) in the same field. Both values
can't be stored in same field. Thus, current encryption
implementation does not support encrypting spatial indexes.

fil_space_encrypt(): Do not encrypt page if page type is
FIL_PAGE_RTREE (this is required for background
encryption innodb-encrypt-tables=ON).

create_table_info_t::check_table_options() Do not allow creating
table with ENCRYPTED=YES if table contains spatial index.

2017-02-08 09:05:15 +02:00

5 lines

124 B

Plaintext

Raw Blame History

 --innodb-encrypt-tables
 --innodb-encryption-rotate-key-age=15
 --innodb-encryption-threads=4
 --innodb-tablespaces-encryption