Manage Local Snapshots

QueryDeck keeps managed Local Snapshots separate from ordinary saved connections.

They appear as SNAPSHOT · LOCAL and can include provenance such as the source connection, root table, age, row count, and table count.

Open the manager

Open the connection switcher and choose Snapshots….

The manager lists every QueryDeck-managed snapshot and its current backend and runtime state.

Docker snapshots

For managed Docker snapshots you can:

• open the snapshot;
• start a stopped container;
• stop a running container;
• delete the snapshot and its owned container/volume;
• inspect known storage usage.

QueryDeck stops managed snapshot containers when the app exits, but it does not delete their volumes. Opening the saved snapshot later starts the owned container again.

Local PostgreSQL snapshots

For QueryDeck-created local PostgreSQL databases you can:

• open the snapshot;
• delete the generated database through the managed cleanup path.

Delete all snapshots

Delete All Snapshots… sends every managed snapshot through the same ownership-aware deletion path used for individual snapshots.

QueryDeck does not use broad Docker prune commands.

Clean orphans

If a QueryDeck-owned container or volume exists without a matching saved snapshot, the manager can surface it as an orphan.

Clean Orphans… re-checks QueryDeck ownership immediately before deletion. Resources whose ownership cannot be proven are skipped rather than removed.

External changes

If you manually delete or replace snapshot infrastructure outside QueryDeck, the saved connection can show states such as missing resource or ownership mismatch.

QueryDeck will not silently adopt an unrelated Docker resource just because it reused the same name.

Next

• Local Snapshot overview
• V1 limitations