Daniel Westermann

PostgreSQL: Dropping a table automatically if another table is dropped

Imagine the following use case: You have a table t1, and based on it’s contents you create another table t2. What you want to achieve is: If table t1 gets dropped, you want to have table t2 to be dropped(…)

2022.pgconf.eu, what a blast

2022.pgconf.eu is currently happening in Berlin. We have a record number of 600 attendees, this makes it the largest ever PostgreSQL Conference Europe and we’re hitting the hard limits of the venue.

Meson vs. make: PostgreSQL build and test times

In the last post we’ve looked into how you can build PostgreSQL with Meson instead of the traditional way using configure/make. The reason for this was a thread(…)

Building PostgreSQL with Meson

Last year, around this time, there started a thread on hackers which was about building PostgreSQL with meson. I didn’t know anything about Meson at this time, and don’t know much more(…)

PostgreSQL from packages on NetBSD

The last flavor of BSD we’ll look at is NetBSD. We already had FreeBSD (here and here) and OpenBSD (here and(…)

PostgreSQL from source on OpenBSD

In the last post we’ve seen that it is quite easy to get started with PostgreSQL on OpenBSD when you install from the provided packages. The downside of this was, that not the latest version of(…)

PostgreSQL from packages on OpenBSD

Almost all of our customers run PostgreSQL on one of the distributions of Linux, either installed from packages or from source code. But there is not only Linux, there a various flavors of BSD you can(…)

How to contribute to YaK

Some days ago we officially launched YaK, which is our open source tool for deploying infrastructures everywhere. Because the core component of Yak is open source, can you contribute if you want. Contributions are more than(…)

Be careful with “public” in PostgreSQL

PostgreSQL comes with the "public" schema by default and we always recommend to drop it for PostgreSQL versions up to 14. The reason is, that everybody who is able to connect to a database, by default, can create objects in(…)

Do you really need varchar(n) in PostgreSQL?

PostgreSQL comes with three data types for storing characters. char, varchar and text. What we often see at our customers is, that varchar(n) is used when they want to store characters and limit the amount of characters which are allowed(…)