Infrastructure at your Service
The last post about Db2 was about getting it up and running. As the issue we had to solve was about performance, getting an explain plan for the problematic statement(s) was the obvious step to do. In PostgreSQL you can just use EXPLAIN for that, and you’re done. In Db2 the procedure is a bit different, but once you know the tools, it is quite easy as well.
Some time ago I’ve written about migrating a CentOS 8 machine to Red Hat 8, because CentOS 8 reached end of life last December. We did that for all CentOS 8 installations at that customer and all are running as virtual machines. The very same customer has many EC2 instances running on CentOS 7. Migrating away from CentOS 7 is one of the next tasks to complete, as CentOS 7 will reach end of life…
My last contact with IBM Db2 was more than 10 years ago, and that only on the SQL/application level. I’ve never done an installation of Db2 as most of our customers either don’t use it, or we don’t know about it, or these databases are managed by other teams than those we work with. And now we have a request for supporting someone with performance issues on Db2, and requests are showing up from people…
By the end of the last post we finished with a running Zabbix server which uses PostgreSQL as it’s back-end database. In addition a Zabbix agent is running on the same host, so the monitoring host itself is present in the Zabbix console. In this post will deploy the Zabbix agent on three PostgreSQL Patroni nodes and later on configure Zabbix to monitor the PostgreSQL instances.
PostgresBuild2021 is currently ongoing and as usual, I had questions after my talk I could not immediately answer. One of the best ways to learn, is to present a topic. There are for sure questions you never thought about. The topic of my talk was “An introduction to server side programming” and I wanted to give people easy examples about how to write procedures and functions in PostgreSQL. It was not about control structures like…
We are often asked which monitoring solution we recommend for PostgreSQL, by people attending our PostgreSQL workshops. We usually answer: What do you have in place already? If a solution already is in place, the most obvious way is trying to integrate into the existing solution. If nothing is there already, you have plenty of choices. You can find some of them on this blog, but the list is quite old. Usually, PostgreSQL is not…
We have quite a few customers still running on CentOS 8 and you probably already are aware that CentOS 8 will be end of life by the end of this year. This forces a lot of companies to either switch to an alternative or to stick with CentOS stream. For most enterprise workloads CentOS stream is not a solution as it is rolling release, and if you want to keep a Red Hat compatible enterprise…
When it comes to backup and restore of PostgreSQL we usually recommend pgBackRest to our customers. This tool comes with many options and features and should bring everything you need. Most of the times we install a dedicated backup host for pgBackRest, which centralizes all backups of the PostgreSQL instances. Sometimes we have several of those, e.g. one for production instances, another for test and development or even a dedicated one for development. How you…
Last week PostgreSQL 14.1, and all other minor versions for the supported version of PostgreSQL have been released. As usual, it is highly recommended to update to the latest minor release as soon as possible. Minor version updates of PostgreSQL are just a matter of installing the new binaries, shutting down the old cluster and starting it up again using the new binaries, that’s it. If you are using packages the procedure is to shutdown…
PostgreSQL 15 will probably come with a new feature for pg_dump: Instead of passing the arguments/options directly to pg_dump when it is executed, you may also use a file to describe what you want to export. In the Oracle world it was (maybe still is, but I don’t know) very popular to do that with traditional exp/imp and the expdp/impdp utilities. pg_dump did not know that feature but this will probably change for PostgreSQL 15….
