--- title: "I Dropped a Table in Production—Now What?" url: https://daily.dev/posts/i-dropped-a-table-in-production-now-what--gtobxlrtt source_url: https://neon.com/blog/recover-production-database type: article source: "Neon" published: 2026-07-09T06:57:40.027Z updated: 2026-07-09T07:00:33.338Z tags: ["postgresql"] reading_time: 8 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # I Dropped a Table in Production—Now What? **[Neon](https://daily.dev/sources/neontech)** · 8 min read · 0 upvotes · 0 comments ## Summary When you accidentally drop a table in a multi-terabyte production Postgres database, Neon's instant Point-in-Time Recovery (PITR) lets you restore to the exact moment before the drop in about one second, regardless of database size. Two recovery routes are outlined: (1) keep production running and copy the missing table from a PITR branch — preserving post-incident data — or (2) fully rewind production to the pre-drop state by swapping branches under the same endpoint without changing connection strings. Both approaches leverage Neon's copy-on-write storage model, which avoids the slow snapshot-restore and WAL-replay process required by AWS RDS, where multi-TB restores can take hours. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/i-dropped-a-table-in-production-now-what--gtobxlrtt)