From: Sumit Sengupta <ssengupta@hotmail.com>
To: Inzamam Shafiq <inzamam.shafiq@hotmail.com>
To: noloader@gmail.com <noloader@gmail.com>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: PostgreSQL vs MariaDB
Date: Fri, 24 Mar 2023 16:17:03 +0000
Message-ID: <DM4PR84MB1830AF9087568B9A8DDF983EB3849@DM4PR84MB1830.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAH8yC8=4TqUBgcy=WMMtgN=0R46+h341jzr-8bEdRjrvQoRAyw@mail.gmail.com>
References: <AM9P251MB0330EB09C5F1DFB27587402E98849@AM9P251MB0330.EURP251.PROD.OUTLOOK.COM>
<CAH8yC8=4TqUBgcy=WMMtgN=0R46+h341jzr-8bEdRjrvQoRAyw@mail.gmail.com>
Here is an EDB presentation on this from 2019
https://www.enterprisedb.com/blog/postgresql-vs-mysql-360-degree-comparison-syntax-performance-scala...
PostgreSQL vs. MySQL: A 360-degree Comparison [Syntax, Performance, Scalability and Features]<https://www.enterprisedb.com/blog/postgresql-vs-mysql-360-degree-comparison-syntax-performance-scala...;
In this blog, we will discuss the key differences in terms of performance, syntax, scalability, and features between PostgreSQL and Mysql. PostgreSQL and MySQL are both immensely popular open-source databases, and a variety of real-time applications today utilize both. MySQL is known to be the world’s most popular database, whereas PostgreSQL is known as the world’s most advanced RDBMS database.
www.enterprisedb.com
________________________________
From: Jeffrey Walton <noloader@gmail.com>
Sent: Friday, March 24, 2023 10:49 AM
To: Inzamam Shafiq <inzamam.shafiq@hotmail.com>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: PostgreSQL vs MariaDB
On Fri, Mar 24, 2023 at 7:07 AM Inzamam Shafiq
<inzamam.shafiq@hotmail.com> wrote:
>
> Can someone please list pros and cons of MariaDB vs PostgreSQL that actually needs serious consideration while choosing the right database for large OLTP DBs (Terabytes)?
>
For me, security is important. I don't want to do a lot of late night
patching, and I don't want to cleanup after a data breach. When
vendors pitch a product with a database, I insist on a PostgreSQL
backend.
MySQL makes regular appearances on BugTraq. MySQL has over 1700 CVEs
going back to 1999.[1] It tells me there are problems with the
engineering process.
MariaDB adds additional CVEs on top of MySQL, but the count appears
low. I have never separated the purely MariaDB flaws from the
underlying MySQL flaws.
In contrast, PostgreSQL has about 240 CVEs going back to 1999.[2] It
tells me PostgreSQL has a better engineering process.
Jeff
[1] https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=MySQL
[2] https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=PostgreSQL
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ssengupta@hotmail.com, inzamam.shafiq@hotmail.com, noloader@gmail.com
Subject: Re: PostgreSQL vs MariaDB
In-Reply-To: <DM4PR84MB1830AF9087568B9A8DDF983EB3849@DM4PR84MB1830.NAMPRD84.PROD.OUTLOOK.COM>
References: <AM9P251MB0330EB09C5F1DFB27587402E98849@AM9P251MB0330.EURP251.PROD.OUTLOOK.COM> <CAH8yC8=4TqUBgcy=WMMtgN=0R46+h341jzr-8bEdRjrvQoRAyw@mail.gmail.com> <DM4PR84MB1830AF9087568B9A8DDF983EB3849@DM4PR84MB1830.NAMPRD84.PROD.OUTLOOK.COM>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox