Neues vom PostgreSQL Planet

In my day to day, I'm surrounded by great database engineers. They talk about things like HA and raft protocol and the right and wrong approach for configuring synchronous vs. asynchronous replication. There is a lot of value in all that deep technical knowledge, but for when interacting with customers, I like to boil it down a bit.

Something that can be useful when running PostgreSQL on FreeBSD.

Preventing FreeBSD to kill PostgreSQL (aka OOM Killer prevention)

There are a lot of interesting articles on how to prevent the Out of Memory Killer (OOM killer in short) on Linux to ruin you day, or better your night. One particular well done explaination about how the OOM Killer works, and how to help PostgreSQL to survive, is, in my humble opinion, the one from Percona Blog.

On 29th of March 2021, Peter Eisentraut committed patch: Add unistr function   This allows decoding a string with Unicode escape sequences. It is similar to Unicode escape strings, but offers some more flexibility.

Sometimes you just have to work with binary in your PostgreSQL database, and when you do the bytea type is what you’ll be using. There’s all kinds of reason to work with bytea:

On 26th of March 2021, Noah Misch committed patch: Add "pg_database_owner" default role.   Membership consists, implicitly, of the current database owner. Expect use in template databases. Once pg_database_owner has rights within a template, each owner of a database instantiated from that template will exercise those rights.   Reviewed by John Naylor.

The previous series addressed isolation and multiversion concurrency control, and now we start a new series: on write-ahead logging.

Ansible has a very useful module "postgresql_ping" which checks connectivity to the database server.

On 24th of March 2021, Peter Eisentraut committed patch: Add date_bin function   Similar to date_trunc, but allows binning by an arbitrary interval rather than just full units.

While migrating to PostgreSQL, some of the users may be curious about the type of replication offered by PostgreSQL. Some might want to know if they have to pay any additional enterprise license in order to achieve this requirement. This is because, a few commercial databases require a customer to take an enteprise license to setup replication. But, PostgreSQL, like advanced Open Source databases, automatically offers several types of replication methods built-in.

Logging is an important topic and particularly useful for troubleshooting, debugging and monitoring. Many applications have their own build-in logging mechanism. Pgpool-II logging mechanism is similar to PostgreSQL logging mechanism. Pgpool-II log management system supports two ways for logging messages (stderr and syslog) and the logging collector process collects the logs sent to stderr and redirects them into log files. However, how can we manage the logging system on Kubernetes? In this blog, I will describe how to manage Pgpool-II container logs on Kubernetes.

© Laurenz Albe 2021

Users with an Oracle background consider tablespaces very important and are surprised that you can find so little information about them in PostgreSQL. This article will explain what they are, when they are useful and whether or not you should use them.

Post Views: 0 Introduction What is Greenplum Database? This is on of PostgreSQL forks optimized for OLAP and analytics workloads. In my opinion the second life of GreenplumDB began in 2015 year. In this year Greenplum became the open source project. The current 6 version...

With the rise of Postgres, new organizations are evaluating how to benefit from its power and flexibility. As that evaluation progresses, Postgres advocates must address the question, "Is Postgres secure?"

PostgreSQL Person of the Week Interview with Jan Karremans: I was born in a very small village in the south of the Netherlands. From there I ended up, through a short time of living in Germany, at the German Border in the Middle East of The Netherlands.

A glance at Raku implementation for PostgreSQL database connectivity.

Introduction

Currently, the global PostgreSQL development team, led by Amit Kapila, continues to contribute to the community as part of Fujitsu's work on PostgreSQL. As a member of this team, I am actively working with talented and passionate community members around the world to advance PostgreSQL.

Our team will publish blog posts focusing on the features and patches that members have worked on. This article discusses "Batch Insert to Foreign Table" committed to PostgreSQL 14, explaining why we've worked on it and the resulting exciting performance improvements.

One of the performance projects I’ve focused on in PostgreSQL 14 is speeding up PostgreSQL recovery and vacuum. In the PostgreSQL team at Microsoft, I spend most of my time working with other members of the community on the PostgreSQL open source project.

An interesting extension that helps removing bloating from tables and databases.

A simple view to see if a user can perform backups.

We at Crunchy Data put as much development effort into improving GEOS as we do improving PostGIS proper, because the GEOS library is so central to much geospatial processing.