this post was submitted on 06 Sep 2026
324 points (95.8% liked)
Technology
87877 readers
2730 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah sorry, that’s what I meant by testing stuff. I suppose if you’re always testing things in the DB, it makes sense. Usually in my case, I would spin up a Postgres instance only for the week or so that I’m developing and testing with it. Eventually I push to cloud though. I don’t keep it running locally unless I’m testing a change. But I’m not testing changes often… I wouldn’t consider it part of my stack for that reason. I might run a local RDBMS a few times a year.
On the other hand, I will use SQLite or DuckDB all the time for local work. Not sure if those count as RDBMS, they are serverless.
I won’t never consider a local RDBMS as having stable data storage, so it falls into a strictly “testing” category for me, I guess “development and testing” is more accurate.
I could totally see that for the web stuff where I only make changes a couple of times a year. Usually when working on those I just delete the local DB before I start to keep it clean, but spinning up a new copy would be more efficient.
For our desktop apps / server Postgres is always installed locally on the machine, so keeping it there mirrors "production".
I spent most of my time working on those apps and services, or working on the Android client (or both at the same time when a feature requires that both change), and often on a copy of actual customer data as we do a lot of custom work for clients.
Yeah, that’s exactly the process- while you are building out a feature it hits a local DB and once it’s ready to integrate you push it to a shared environment.
If you break dev, coworkers be mad