Jan Lindström f8cacd03a7 MDEV-8143: InnoDB: Database page corruption on disk or a failed file read ... 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.		2015-05-14 11:32:24 +03:00
..
srv0conc.cc	fixing embedded: WaaS. Wsrep as a Service.	2014-10-01 23:48:34 +02:00
srv0mon.cc	InnoDB/XtraDB Encryption code cleanup	2015-04-07 23:44:57 +02:00
srv0srv.cc	s/innodb_default_encryption_key/innodb_default_encryption_key_id/	2015-04-10 02:40:10 +02:00
srv0start.cc	MDEV-8143: InnoDB: Database page corruption on disk or a failed file read	2015-05-14 11:32:24 +03:00