Closed marco44 closed 5 years ago
We should also explicitly show on the UI that the database has been dropped. Would you like to keep track of when approximatively the database has been dropped, of the end of any activity is enough?
Also, obvisouly a lot of features won't work, like doing explain of related queries, but there's nothing we can do about it.
End of activity is enough, I think. But storing the date when the database has been dropped in a table won't kill performance :)
Some preliminary work has been done :
Some work is still needed for some corner cases, like if a database is renamed and a snapshot didn't occur for instance.
The limitations I was mentioning are probably not critical, and we already keep track of deleted and renamed database. I'm closing this issue. If you think more could be done, please open a new issue in powa-archivist project!
Currently, when a database is dropped, we lose its data in the GUI: everything is stored with the dbid.
We should have a powa_pg_database_history to keep track of all seen databases: