Both are open source databases. This is old debate. Yes no one can expect one database fits all your jobs.
To choose between the two databases, you need to understand whether you need the transaction support of Postgres or the large-text-area support in MySQL.
From the article:
It’s interesting that the two databases appear to be converging to meet in the middle somewhere. While MySQL is working on adding transaction support and slowly adding features like subselects, Postgres is making progress in the performance and stability.
It compare two databases using following points:
- SQL standard COMPLIANCE
- PLATFORMS
- Speed
- STABILITY
- DATA INTEGRITY
- SPECIAL server-side FEATURES
- Security
- LOCKING and CONCURRENCY SUPPORT
- LARGE OBJECTS etc
A good read (little old too) but don’t forget to make some test running before selecting your database.
🐧 1 comment so far... add one ↓
Category | List of Unix and Linux commands |
---|---|
File Management | cat |
Firewall | Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04 |
Network Utilities | dig • host • ip • nmap |
OpenVPN | CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04 |
Package Manager | apk • apt |
Processes Management | bg • chroot • cron • disown • fg • jobs • killall • kill • pidof • pstree • pwdx • time |
Searching | grep • whereis • which |
User Information | groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w |
WireGuard VPN | Alpine • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04 |
There’s a WikiVS page on this topic. It has a lot of up-to-date information:
http://www.wikivs.com/wiki/MySQL_vs_PostgreSQL
Plus, you can contribute to the comparisons, wiki-style.