5 ms·
I'm super tempted to move from MySQL to postgres, but, we are currently self hosting and MySQL is breeze to run. My only experience with postgres is running a b
by patrickdavey 5y ago
I'm super tempted to move from MySQL to postgres, but, we are currently self hosting and MySQL is breeze to run. My only experience with postgres is running a brew update and it completely borking the database and having to track down some cryptic post in order to fix it. Also, as pointed out elsewhere, MySQL seems not to require vacuuming or anything else. It's the unknowns of moving which make me nervous.
- throwawayboise 5y agoModern postgres vacuums automatically. It's as easy to set up and run as MySQL for simple scenarios.
- dirkt 5y ago> running a brew update and it completely borking the database I also ran into this, but to me it more looks like in issue with how Homebrew does Postgres. Also, keeping different versions of Postgres around with Homebrew is a bit of a PITA.
- Bayart 5y agoFor self-hosting one instance, there's little difference. What matters more is how well the tooling you use with with your DB supports it. Recently I've been on a .NET 6.0 project and the Entity Framecore Core MySQL provider was broken for what I was doing. The one for Postgres worked fine so we chose that. >My only experience with postgres is running a brew update and it completely borking the database and having to track down some cryptic post in order to fix it. I find containers work wonders for databases, whether it is for using specific versions, segregating instances, keeping your system clean etc. I keep at least one of MySQL, Mango, MSSQL and Postgres running at all times. I would never install one natively.