Infrastructure at your Service

All Posts By

Daniel Westermann

Daniel Westermann

Auditing with EDB Postgres Enterprise

By | Database Administration & Monitoring | No Comments

It might be that there is a requirement to audit operations in the database. Maybe because of legal requirements, maybe because of security requirements or whatever. I’ve already written a post in the past describing what you can do in community PostgreSQL, this post is specific to EDB Postgres. The auditting features come be default in EDB Postgres and you do not need to install any extension such as pgaudit.

Read More
Daniel Westermann

Working with files on the filesystem in PostgreSQL

By | Database Administration & Monitoring | No Comments

PostgreSQL comes with various helper functions that support you with working with files on the filesystem on the host PostgreSQL is running on. You might ask yourself why that is important but there are use cases for that. Maybe you want to list the contents of a directory because new files that showed up since the last check do trigger something. Maybe you want to load a file into the database (which you also can…

Read More
Daniel Westermann

Using Ansible to bring up a three node Patroni cluster in minutes

By | Database Administration & Monitoring | No Comments

Automation is key today, nobody wants to do the same tasks over and over and again. Cloud without automation is not even possible. There are several tools around that help with automation and one of the most popular is Ansible. We already have several posts about Ansible on our blog platform but this one will be rather long. Setting up PostgreSQL high available architectures is our daily business and we as well try to automate…

Read More
Daniel Westermann

PostgreSQL 12: log_statement_sample_rate

By | Database Administration & Monitoring | No Comments

A common way to identify long running queries in PostgreSQL is to set log_min_duration_statement to a value that is known to cause troubles. In other words: If you know most of your statements usually execute in under a second you could set log_min_duration_statement to “2s” (which means two seconds) so that whenever a statement takes longer than two seconds it will be reported in the log file. The issue with this however is, that this…

Read More