Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Zabbix Postgres vs MySQL – Pros and Cons to decide

by | Feb 20, 2021

Having second thoughts on Zabbix Postgres vs MySQL? Let us see which RDBMS should you choose.

With more than a decade of expertise in managing servers, we have found that PostgreSQL and MySQL perform almost the same when used as Zabbix Database.

However, we’ll do an analysis on Zabbix Postgres vs MySQL and see what makes them unique from each other.

As part of our Server Management  Services, we help customers to choose the right DBMS.


Zabbix Postgres vs MySQL

Postgres is the advanced and powerful SQL compliant and open-source objective-RDBMS. Whereas, MySQL is the most popular and commonly used RDBMS.

Recently, we had a customer stuck with choosing between PostgreSQL and MySQL for his Zabbix. Since his requirement was to run more complex queries we suggested PostgreSQL. It is more stable in heavy io situations.

Based on our customer requirements, our Engineers suggest the best as both Postgres and MySQL RDBMS have their own pros and cons.


What makes Zabbix Postgres different from MySQL?

There is a tremendous increase in the number of devices such as servers and network equipment in the enterprise data centers due to new technologies like cloud computing.

So, monitoring a huge number of devices is becoming more and more important nowadays.

Zabbix being the most popular open-source monitoring software uses one among MySQL, PostgreSQL, Oracle, DB2, and SQLite as a database to store both histories and other information.

All the above-mentioned DBs are categorized as RDBMS and widely in use for various applications.

Moving ahead, let’s see which among Postgres and MySQL are suitable for Zabbix.


What are the pros and cons of Postgres vs MySQL?

  • Pros

The foremost advantage of Postgres is it is fully ACID(Atomicity, Consistency, Isolation, Durability) compliant.

So, it is best opted by corporations that perform complex and high-volume data operations.

Regarding the performance, both are almost the same. But, due to less i/o wait, Postgres is one step ahead.

One of the advantages of choosing MySQL over Postgres is less CPU consumption and is easier to handle.

We all understand the advantages and disadvantages in a situation where we face some trouble.

One of the most important in case of trouble with Databases is backups. Postgres offers a hot backup and point in time restore.

  • Cons

Yes, it is certain that every up has its downs. Let us now walk through the downs of Postgres and MySQL.

As we are comparing this in point of Zabbix, the data backup is the most crucial one.

But, MySQL alone is not providing any hot backup utility. Hot backup means, taking the backup without affecting the users and without any downtime.

Instead, InnoDB provides this by InnoHotBackup. So, if we are using MyISAM then there will be no hot backup utility available.

Also, MySQL is not suitable in scenarios where large systems where data needs to be authenticated and read/write speeds are critical for success.

And, now it is owned by Oracle Corporation and offers several paid editions.

In addition, compared with MySQL, PostgreSQL is a little slow. Also, tweaking is not easy compared with MySQL.

[Not sure of your choice? Our Experts are available 24/7.]



In short, our Support Engineers always choose the best options especially when there is conflict in making the decision. Today, we discussed Zabbix Postgres vs MySQL in detail and saw the criteria to choose between them.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.