This issue happens on production of one user that enabled Sentry:

![Screenshot_20210303_002028](https://user-images.githubusercontent.com/18581488/109716945-7f9a1200-7bb6-11eb-8cf4-1080ad535d18.png)

Build id: 49938CCB63EE2A4E16CF0528307EE15F08469219.
create.if_not_exists = false;
        WriteBufferFromOwnString statement_buf;
        formatAST(create, statement_buf, false);
        writeChar('\n', statement_buf);
        String statement = statement_buf.str();
        
        WriteBufferFromFile out(metadata_file_tmp_path, statement.size(), O_WRONLY | O_CREAT | O_EXCL);
        writeString(statement, out);
        out.next();
        if (context.getSettingsRef().fsync_metadata)
            out.sync();
        out.close();
    }
    
    auto db_guard = DatabaseCatalog::instance().getExclusiveDDLGuardForDatabase(database_name);
    bool added = false;
    bool renamed = false;
    try
    {
        
        DatabaseCatalog::instance().attachDatabase(database_name, database);
        added = true;
        if (need_write_metadata)
        {
            
            renameNoReplace(metadata_file_tmp_path, metadata_file_path);
            renamed = true;
        }
        database->loadStoredObjects(context, has_force_restore_data_flag, create.attach && force_attach);
    }