using postgres since late 2000. in those 23 years, i had exatly 0 data losses due to the db making a fault. it was always "operator error". scalability is a bit harder to do with postgres maybe, but it's doable (like partitioning tables and distributing partitions over several machines), with additional read replicas to separate read/write load, although your application of course has to send read and write queries to separate instances then. one more interesting fact is that afaik the SQLite project does something called "wwpd" in their test cycles. this reads "what-would-postgres-do", so basically they completely ignore what sqlserver or mysql are doing and instead fix their code until the output is 1:1 that of postgres 😄
Question: You said MySQL supports pluggable storage engines - INNODB (ACID compliant) & MyISAM (non-ACID compliant) where Postgres supports only MyISAM In the explaination of Postgres you said, its full ACID Complient Isn't that contradicting?
Good job! This is the 4th video I've seen on this and the first one to mention the licensing. Which is mainly what i wanted to hear. Amazing how hard it is to find the info you want. Thanks for being smarter than average. (Yes i could have read up on current licences for both....but i get tured of reading)
Saying “speed”, “scalability” or “easy to use” without et least mentioning what gives this characteristics in compare is really harmful for the whole industry Because people will spread this knowledge to one another and this will create and develop technologies that does not deserve to be evolved
When considering data migration between these systems, your ultimate ally is Airbyte. As the leading open-source ELT tool, Airbyte simplifies the migration process, transforming a complex procedure into an intuitive task for engineers.
Just a few things : - Both MySQL and PostgreSQL are fully ACID compliant. (as you should use InnoDB on MySQL) - PostgreSQL doesn't actually have anything bundled for H.A, you have replication but nothing that would trigger and automatic failover for example like would InnoDB clusters (you have to rely on external tool that Stolon that may or may not work or be supported for long) - You have extensibility on MySQL too (via plugins) - MySQL is superior in some of the core security topics like TDE (Transparent Data Encryption) or credential/password management (with password policies, multiple passwords per user for rotations, etc...) - PostgreSQL MVCC is not an advantage actually, it causes TONS of write amplifications and required maintenance (normally automated with autovacuum), InnoDB is vastly superior on this case. A few issues with MySQL still today : - No UUID type - Triggers would not execute on foreign tables modifications (big issue for some case if you rely a lot on triggers)
Great points. I think maybe where Postgres is more ACID compliant is with DDL statements as Postgres supports transactional DDL. Also, MariaDB could be a great MySQL alternative if a UUID datatype is required (and for other reasons as well, although there are trade-offs).
Hey Airbyte, really nice video! I was wondering if I could help you edit your videos and also make a highly engaging Thumbnail which will help your video to reach to a wider audience
I only hate the importing features in postgres. Very devastating. If someone could tell me how to import a very large csv file in Postgres without typing out all the columns, i will be greatful
@@berrybush6545 I think he's confused on the difference between ending a product entirely and declaring that older versions are EOL. Oracle is not ending MySQL.
using postgres since late 2000. in those 23 years, i had exatly 0 data losses due to the db making a fault. it was always "operator error". scalability is a bit harder to do with postgres maybe, but it's doable (like partitioning tables and distributing partitions over several machines), with additional read replicas to separate read/write load, although your application of course has to send read and write queries to separate instances then. one more interesting fact is that afaik the SQLite project does something called "wwpd" in their test cycles. this reads "what-would-postgres-do", so basically they completely ignore what sqlserver or mysql are doing and instead fix their code until the output is 1:1 that of postgres 😄
Your video broadened my understanding of both databases.
Thank you!
Question:
You said MySQL supports pluggable storage engines - INNODB (ACID compliant) & MyISAM (non-ACID compliant) where Postgres supports only MyISAM
In the explaination of Postgres you said, its full ACID Complient
Isn't that contradicting?
Good job! This is the 4th video I've seen on this and the first one to mention the licensing. Which is mainly what i wanted to hear. Amazing how hard it is to find the info you want. Thanks for being smarter than average. (Yes i could have read up on current licences for both....but i get tured of reading)
Glad it was helpful!
make it simple - MySQL is table based relational db... Posgres is more "object" based relational db.
Which one company prefers to use
Saying “speed”, “scalability” or “easy to use” without et least mentioning what gives this characteristics in compare is really harmful for the whole industry
Because people will spread this knowledge to one another and this will create and develop technologies that does not deserve to be evolved
Great breakdown, very useful! I don't know why but I thought postgres was much newer. Had no idea how mature it really was
When considering data migration between these systems, your ultimate ally is Airbyte. As the leading open-source ELT tool, Airbyte simplifies the migration process, transforming a complex procedure into an intuitive task for engineers.
I wish to use PostGreSQL more, but MySQL is more advanced, suits to more products (like WordPress) and more documented and supported.
Why would you think MySQL is more advanced? 🤨
Hey what about scalability if using PostgreSQL?
It is every bit as easy to scale a PostgreSQL server as a MySQL server.
Very good and relevant video, thank you
Nice explanations !! Thank you for the content!
Postgres embrace the concept of schemas, that are basically bd's inside a singular DB.
what "bd's" mean?
@@esdegan7176 Sorry, I mean DataBase, because in portuguese we use the short "BD" for "Banco de Dados".
Just a few things :
- Both MySQL and PostgreSQL are fully ACID compliant. (as you should use InnoDB on MySQL)
- PostgreSQL doesn't actually have anything bundled for H.A, you have replication but nothing that would trigger and automatic failover for example like would InnoDB clusters (you have to rely on external tool that Stolon that may or may not work or be supported for long)
- You have extensibility on MySQL too (via plugins)
- MySQL is superior in some of the core security topics like TDE (Transparent Data Encryption) or credential/password management (with password policies, multiple passwords per user for rotations, etc...)
- PostgreSQL MVCC is not an advantage actually, it causes TONS of write amplifications and required maintenance (normally automated with autovacuum), InnoDB is vastly superior on this case.
A few issues with MySQL still today :
- No UUID type
- Triggers would not execute on foreign tables modifications (big issue for some case if you rely a lot on triggers)
Great points. I think maybe where Postgres is more ACID compliant is with DDL statements as Postgres supports transactional DDL. Also, MariaDB could be a great MySQL alternative if a UUID datatype is required (and for other reasons as well, although there are trade-offs).
Great video! I remember this guy on his other channel, what was his name again? Thanks :)
Chris sean
< 3
I regret spending 10 min on this video, 0 useful technical information, only broad statements, and some of them are not even entirely truthful
that's why they got rid of this guy lmao
Thankyou this is really helpful
Glad it was helpful!
nice explanation, thanks
Thank you bro. Very helpfull.
Engineers always telling the world they are engineers. "As an engineer, everyone needs to know I'm an engineer"
Thanks for this video - joined as a sub
It's safe to say Airbyte is slowly going out of business.
Can you elaborate?
Hey Airbyte, really nice video! I was wondering if I could help you edit your videos and also make a highly engaging Thumbnail which will help your video to reach to a wider audience
I only hate the importing features in postgres. Very devastating.
If someone could tell me how to import a very large csv file in Postgres without typing out all the columns, i will be greatful
It has a lot of columns tho? 'cause you can use COPY, but I guess you already know this command and looking for another answer,
@@brayanclavijo5458
I've tried to use this copy command but I always get errors
Can someone pls guide me, which database is preferable for core banking domain between mssql and postgresql?
apart from Oracle.
👍
You should have mentioned MySQL was forked over to Maria db and that oracle will end of life it soon.
@@berrybush6545 I think he's confused on the difference between ending a product entirely and declaring that older versions are EOL. Oracle is not ending MySQL.
i hear "soon" from day 1 mariadb was born :D
Makasih, Video nya sangat bermanfaat bagi saya, ini akan lebih membantu saya jika anda menambahkan subtitle bahasa Indonesia di video mu
Yeah I’ll have to downvote this, just saying that MySQL is in general more performant is highly misleading and harmful to the industry.
Just downvoted your comment 😅
mysql is easier to manage.