postgres=# select * from sessions where video_id = 'l-0IP-_meD0';
Simplify recovering from a DROP TABLE
Log a recovery landmark when destructive DDL commits.
session summary
The group designed a recovery landmark for accidental DROP TABLE. They first considered emitting a named restore-point WAL record, then traced deletion through parser, dependency, permission, and lock paths. Rollback and the absence of a fresh LSN before any WAL write made that design misleading. They pivoted to logging a restore LSN after the table lock is acquired but before deletion, restricted it to ordinary tables, demonstrated the output, and prepared a small pgsql-hackers patch.
timecodes
- Two recovery and restore ideas
- Choosing the DROP TABLE recovery problem
- Considering an automatic restore-point record
- Which dropped objects need protection
- Tracing DROP through parser and dependency code
- Intent, permissions, locks, and rollback
- Why no usable LSN exists before WAL
- Final log message and mailing-list patch