ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Restoring a database snapshot beyond the plan retention window The goal is to recover a Supabase project database from a daily backup that falls outside the current plan's retention period. On the free tier, automated backups are retained for seven days; paid plans extend this to thirty days. Point-in-time recovery is only available on Pro and higher plans.
Goal: restore a Notion workspace to a specific point in time while preserving the original internal page IDs so that existing links, databases, and embedded references remain functional after recovery. Constraint: Notion’s native export (Settings → Export) produces Markdown/CSV/JSON files that lack page UUIDs, and importing those files creates new IDs, break
DynamoDB Point-in-time recovery (PITR) restores a table to any second within the last 35 days, including the schema that existed at that timestamp. When a schema change such as adding or removing a Global Secondary Index is rolled back by restoring to an earlier point, the restored table reflects the previous schema, but all writes made after the restore tim
Restore goal I need to restore an online backup taken with neo4j-admin backup into a Neo4j 5.x instance, and the backup was created on an earlier major version. The goal is a point-in-time recovery that preserves node and relationship counts, indexes, and any stored procedures or user-defined functions, without a separate manual data migration step. Constrai
The goal is to undo a single DDL statement (e.g., dropping a column) on a DigitalOcean Managed Database cluster while keeping all data modifications that occurred after that change. Currently the platform only provides point‑in‑time recovery and full‑cluster backup restores, which replace the entire dataset and terminate existing connections, making a select
supabase
dynamodb