Embed Notice

@tyler On my old remote dev tower, I dumped a backup, sent it to myself with teams because outlook wouldn't let me, then made a new db on the laptop, added the sole read/write system user for the db, then restored the database backup (dba folks have tended to freak out when they learn the app is designed around a single db user)

this is the most I will ever touch the db, it is purely for dev and thankfully/unfortunately, the vendor owns the cloud version of the software we work on so we cannot touch any of the databases

for my own local stuff, I never touch postgres - but I don't really have a choice for this because they have so screwed up their production code that it no longer starts with a clean database

once that works (or doesn't), and people stop hounding me for stuff, I will try the approach you described in hopes it is quicker - the databases occasionally get locked into a corrupted state so backups needs to be restored, but otherwise I don't touch it

this is all local only