An error occurred fetching the project authors.
- 09 Jun, 2015 2 commits
-
-
Jan Lindström authored
MDEV-8268: InnoDB: Assertion failure in file buf0buf.cc line 5842 failing assertion ut_a(free_slot != NULL); Analysis: Problem is that there is not enough temporary buffer slots for pending IO requests. Fixed by allocating same amount of temporary buffer slots as there are max pending IO requests.
-
Jan Lindström authored
Removed memcpy's on cases when page is not encrypted and make sure we use the correct buffer for reading/writing.
-
- 04 Jun, 2015 1 commit
-
-
Jan Lindström authored
MDEV-8250: InnoDB: Page compressed tables are not compressed and compressed+encrypted tables cause crash Analysis: Problem is that both encrypted tables and compressed tables use FIL header offset FIL_PAGE_FILE_FLUSH_LSN_OR_KEY_VERSION to store required metadata. Furhermore, for only compressed tables currently code skips compression. Fixes: - Only encrypted pages store key_version to FIL header offset FIL_PAGE_FILE_FLUSH_LSN_OR_KEY_VERSION, no need to fix - Only compressed pages store compression algorithm to FIL header offset FIL_PAGE_FILE_FLUSH_LSN_OR_KEY_VERSION, no need to fix as they have different page type FIL_PAGE_PAGE_COMPRESSED - Compressed and encrypted pages now use a new page type FIL_PAGE_PAGE_COMPRESSED_ENCRYPTED and key_version is stored on FIL header offset FIL_PAGE_FILE_FLUSH_LSN_OR_KEY_VERSION and compression method is stored after FIL header similar way as compressed size, so that first FIL_PAGE_COMPRESSED_SIZE is stored followed by FIL_PAGE_COMPRESSION_METHOD - Fix buf_page_encrypt_before_write function to really compress pages if compression is enabled - Fix buf_page_decrypt_after_read function to really decompress pages if compression is used - Small style fixes
-
- 02 Jun, 2015 1 commit
-
-
Sergei Golubchik authored
-
- 27 May, 2015 1 commit
-
-
Jan Lindström authored
Analysis: Problem was that encryption was skipped. Fixed by making sure that tables with ENCRYPTED=YES are encrypted.
-
- 20 May, 2015 1 commit
-
-
Jan Lindström authored
Make sure that when we publish the crypt_data we access the memory cache of the tablespace crypt_data. Make sure that crypt_data is stored whenever it is really needed. All this is not yet enough in my opinion because: sql/encryption.cc has DBUG_ASSERT(scheme->type == 1) i.e. crypt_data->type == CRYPT_SCHEME_1 However, for InnoDB point of view we have global crypt_data for every tablespace. When we change variables on crypt_data we take mutex. However, when we use crypt_data for encryption/decryption we use pointer to this global structure and no mutex to protect against changes on crypt_data. Tablespace encryption starts in fil_crypt_start_encrypting_space from crypt_data that has crypt_data->type = CRYPT_SCHEME_UNENCRYPTED and later we write page 0 CRYPT_SCHEME_1 and finally whe publish that to memory cache.
-
- 18 May, 2015 1 commit
-
-
Jan Lindström authored
Analysis: Problem was that tablespaces not encrypted might not have crypt_data stored on disk. Fixed by always creating crypt_data to memory cache of the tablespace. MDEV-8138: strange results from encrypt-and-grep test Analysis: crypt_data->type is not updated correctly on memory cache. This caused problem with state tranfer on encrypted => unencrypted => encrypted. Fixed by updating memory cache of crypt_data->type correctly based on current srv_encrypt_tables value to either CRYPT_SCHEME_1 or CRYPT_SCHEME_UNENCRYPTED.
-
- 14 May, 2015 1 commit
-
-
Jan Lindström authored
Analysis: Problem was that we did create crypt data for encrypted table but this new crypt data was not written to page 0. Instead a default crypt data was written to page 0 at table creation. Fixed by explicitly writing new crypt data to page 0 after successfull table creation.
-
- 04 May, 2015 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 18 Feb, 2015 1 commit
-
-
Sergei Golubchik authored
-
- 18 Jan, 2015 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 18 Nov, 2014 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 11 Sep, 2014 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 06 May, 2014 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 05 May, 2014 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 26 Feb, 2014 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 16 Dec, 2013 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 07 Nov, 2013 1 commit
-
-
Sergei Golubchik authored
-
- 07 Sep, 2013 1 commit
-
-
Sergei Golubchik authored
-
- 16 Jul, 2013 1 commit
-
-
Sergei Golubchik authored
-
- 08 May, 2013 1 commit
-
-
Sergei Golubchik authored
-
- 08 Mar, 2013 1 commit
-
-
Sergei Golubchik authored
-
- 28 Feb, 2013 1 commit
-
-
Sergei Golubchik authored
-
- 21 Nov, 2012 1 commit
-
-
Sergei Golubchik authored
-
- 01 Nov, 2012 1 commit
-
-
unknown authored
-
- 12 Oct, 2012 1 commit
-
-
Sergei Golubchik authored
-
- 05 Sep, 2012 1 commit
-
-
Sergei Golubchik authored
-
- 15 Jun, 2012 1 commit
-
-
Sergei Golubchik authored
Percona-Server 5.5.24-rel26.0
-
- 15 Feb, 2012 1 commit
-
-
unknown authored
Files copied from Percona-Server-5.5.20-rel24.1.tar.gz source tarball.
-
- 14 Dec, 2011 1 commit
-
-
unknown authored
Files copied from Percona-Server-5.5.17-rel22.1.tar.gz source tarball.
-
- 21 Nov, 2011 1 commit
-
-
unknown authored
lp:percona-server/5.1, tag Percona-Server-5.1.59-13.0. Merged: revid:ignacio.nin@percona.com-20111016133841-fzpr5s89n13ft1s1
-
- 17 Jul, 2011 1 commit
-
-
Sergei Golubchik authored
-