You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deleting a stream from a database, we currently do it right away, before the database has committed. If we were to end up not being able to commit the database changes (power loss / network disconnection / remote changed before we could commit, etc.), that stream would be lost forever. The proper solution is to delay stream deletes until after we are sure we committed the database.
Originally opened by mike-gc
The text was updated successfully, but these errors were encountered:
When deleting a stream from a database, we currently do it right away, before the database has committed. If we were to end up not being able to commit the database changes (power loss / network disconnection / remote changed before we could commit, etc.), that stream would be lost forever. The proper solution is to delay stream deletes until after we are sure we committed the database.
The text was updated successfully, but these errors were encountered: