In a Flexible Server with azure.enable_temp_tablespaces_on_local_ssd enabled, after a failure occurred and the server was started in another AZ, I saw an event where "CREATE TEMPORARY TABLE" returned "No such file or directory". .
Since we are using a local SSD, it would be natural for the DB objects in temp_tablespace to be lost after an event such as starting on a new, different server, but it doesn't seem like a natural behavior to be unable to execute "CREATE TEMPORARY TABLE". .
Isn't it a bug?
In a Flexible Server with azure.enable_temp_tablespaces_on_local_ssd enabled, after a failure occurred and the server was started in another AZ, I saw an event where "CREATE TEMPORARY TABLE" returned "No such file or directory". .
Since we are using a local SSD, it would be natural for the DB objects in temp_tablespace to be lost after an event such as starting on a new, different server, but it doesn't seem like a natural behavior to be unable to execute "CREATE TEMPORARY TABLE". . Isn't it a bug?