Earlier quoted context omitted.
I'd spawn a new DB for that instance too. It can still go a long way to give you a look at how your application worked in the past.
Am I mistaken in thinking that’s totally ridiculous? Let’s charitably say you can run your app with a 1GB cut down snapshot of production. You’re going to do what, save a snapshot of the database for every commit? Every schema migration? …and then provision that up in a running database server… which is notoriously not container friendly… ? It doesn’t sound very plausible to me. Our database is ~1TB, and the app runs…
Just fire up a fresh DB with some sensible default fixtures.
Or pause an integration test mid-way.
Or call some factories from the REPL.
The last thing in the world I want to do development with is production data. Production data is the data of last resort when nothing else can repro.