Daniel Westermann

PostgreSQL 17: Convert a physical replica to a logical replica using pg_createsubscriber

Logical replication in PostgreSQL came with Version 10, which is already out of support. I’ve written about this a long time ago but the basic building blocks are still the same. Setting(…)

Getting started with Greenplum – 6 – Why Greenplum?

Now that we have the basic knowledge for operating a Greenplum cluster we should talk about why Greenplum can be option and what are the benefits of such a system. Again, here are the previous posts:(…)

Getting started with Greenplum – 5 – Recovering from failed segment nodes

This is the next post in this little Greenplum series. This time we’ll look at how we can recover from a failed segment. If you are looking for the previous post, they are here: Getting started(…)

Getting started with Greenplum – 4 – Backup & Restore – databases

This is the fourth part of the Greenplum blog series, the previous ones are here: Getting started with Greenplum – 1 – Installation, Getting started with Greenplum – 2 – Initializing and(…)

Getting started with Greenplum – 3 – Behind the scenes

If you followed part 1 and part 2 of this little blog series you now have a running Greenplum system. There is one coordinator host and there are two segment hosts. In(…)

Getting started with Greenplum – 2 – Initializing and bringing up the cluster

In the last post we’ve configured the operating system for Greenplum and completed the installation. In this post we’ll create the so called “Data Storage Areas” (which is just a mount point or directory) and initialize(…)

Getting started with Greenplum – 1 – Installation

Because PostgreSQL is fully open source there are many forks of it. One of them is called Greenplum which describes itself as “an advanced, fully featured, open source data warehouse, based on PostgreSQL”. Sounds interesting,(…)

PostgreSQL 17: transaction_timeout

PostgreSQL already comes with various time out parameters when it comes to sessions and statements. There is idle_in_transaction_session_timeout, idle_session_timeout, and there is statement_timeout. All of them are disabled(…)

Disabling “alter system” in PostgreSQL?

Last year there started an interesting discussion on the PostgreSQL development mailing list: Would it make sense to implement something in PostgreSQL which can be used to disable the “alter system” command even for superusers?(…)

PostgreSQL 17: Track skipped rows from COPY in pg_stat_progress_copy

In one of the last posts we’ve looked at how you tell copy to ignore any rows which do not fit into the target table starting with PostgreSQL 17. While this is great, this also hides(…)