Our Metabase instance is connected to a redshift database.
For some of the data we sync to redshift, we start by dropping the old table, re-creating it and then inserting the data all over again. It’s not the most efficient way, but it’s an easy way to capture deletes and schema changes.
My question is, what happens to the meta data that we have created in Metabase when the table it describes is dropped?
It would be sad to see all meta data go away every night 
It gets marked as “not present”.
If the table and columns names remain the same, it should get picked up as present the next time the system checks.
This is apparently not the case for postgres databases, at least for me, all meta data for a table is refetched when a table is dropped and created again with the same name.
This also causes the query builder for all saved cards to loose all information about the source table and fields. Raw sql cards are unaffected.
Related github Issue: https://github.com/metabase/metabase/issues/3331
ugh. sounds like a bug alright.