Question: Is having a non schema-aware DbContextModelSnapshot an issue? It sure looks weird.

[IgorPietraszko]

I have implemented everything as described in your article Entity Framework Core - Changing DB Migration Schema At Runtime and it works great! Thanks a lot for that as I am using this approach to support a multi-tenant setup on PostgreSQL.
I only have one question - what about DbContextModelSnapshot? It is not schema-aware but does not seem to cause me any issues. Its just weird since it always reflects the latest SCHEMA I generated migrations for. Is it possible to make it schema-aware?

[PawelGerr]

The snapshot is being used to detect changes in the model. I recommend using the same schema for creation of new migrations. Otherwise, it could happen that EF creates migrations to change the schema of your tables because the schema in the snapshot differs from the schema in the current model.

It is very likely that the snapshot can be made schewa-aware. Via design-time services we can change almost every part of EF core which is responsible for the generation of the migrations and the snapshot. But, I doubt it is worth the time.