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…
Plenty of apps can run from an empty database, if the data storage is focused on resources you, the user, have created for yourself.
But I imagine that people with their heads in the future are imagining you'll use one of these new database startups (the names escape me) to manage snapshots, seeding from anonymised production data, etc.