PXB-3390: Table Flags Mismatch Causing Assertion Failure in InnoDB Ta…

…blespace

Problem:
========
For every IBD file, we open the file twice.
Datafile::open
Fil_shard::get_file_size

Between these two operations, a general tablespace may become
ENCRYPTION Y->N or N->Y

So the tablespace flags can mismatch. This should be tolerated because

Fix:
----
we track this encryption change and recopy them under lock anyway

storage/innobase/fil/fil0fil.cc

@@ -2824,10 +2824,12 @@ dberr_t Fil_shard::get_file_size(fil_node_t *file, bool read_only_mode) {
   detect encryption from recovery and set the in-memory space->flags
   to be encrypted. So on-disk (flags) may not have encryption set
   but in-memory flags have encryption set (from redo parsing). This
-  happens only with undo because it writes space flags in two separate
-  steps */
+  happens undo because it writes space flags in two separate
+  steps. Also general tablespaces are affected because the encryption is
+  in-place. */
   if ((space->flags != flags) && !(opt_lock_ddl == LOCK_DDL_REDUCED &&
-                                   fsp_is_undo_tablespace(space->id))) {
+                                   (fsp_is_undo_tablespace(space->id) ||
+                                    fsp_is_shared_tablespace(space->flags)))) {
     ib::error(ER_IB_MSG_272, ulong{space->flags}, file->name, ulonglong{flags});
     ut_error;
   }