Neues vom PostgreSQL Planet

A new release of the pgagroal connection pooler.

This topic describes how you can detect and solve PostgreSQL memory availability issues.

 

What happened?

To detect memory availability issue on time, and have an ability to look in some historical metrics of this – you must have some kind of monitoring solution. Today, there is a rich selection of monitoring solutions – you can use any you already have, or install another one. Here we will discuss samples based on Awide management and monitoring solution.

One of the reasons I’ve never strayed far from PostgreSQL is that I am always discovering features that overcome all sorts of interesting problems. Although, to be honest, from time to time I’ve had the feeling that sometimes some features are a solution in search of a problem. Take, for example, exporting transaction snapshots. 

A join is a concept in IT which is widely used and often referred to but rarely really understood. What are the differences between inner joins, outer joins, semi joins and so on? Let’s shed some light on them and see how inner and outer joins really work.

Producing sample data

Before we can get started we need to create some sample data:

A little while ago, we had a few PostgreSQL hackers in a room and someone oversaw me typing something like

git diff REL_14_STABLE...REL_15_STABLE

and they wondered, “oh, I didn’t know about three dots”. My flippant explanation was, “you use three dots when two dots don’t give you the right answer”.

But let’s unpack this.

This

git diff REL_14_STABLE REL_15_STABLE

gives you the complete difference between (the tip of) PostgreSQL 14 and PostgreSQL 15. This will be a huge diff.

Understanding postgres performance fundamentally relies on the communication between the client and the database side process called 'backend' in postgresql. I created a small utility to profile the postgres database connection network communication: connection-profiler

A few months ago we made Citus fully open source. This was a very exciting milestone for all of us on the Citus database engine team. Contrary to folks who say that Postgres is a monolith that can’t scale—Postgres in fact has a fully open source solution for distributed scale, one that’s also native to Postgres. It’s called Citus!

Ha ha, made you look!

This post is not a crazy scam (you be the judge) but just a practical description of using cryptographical algorithms to encrypt and decrypt data inside PostgreSQL.

Encryption in Crunchy Bridge

There's already a lot of encryption in Crunchy Bridge!

PostgreSQL Person of the Week Interview with Karen Jex: I’m originally from the North West of England and I lived in various different parts of the country before settling in the South East, commuting to London from Essex for the first few years of my working life as a DBA. I’ve spent my whole career working with databases, and I’m currently a Solutions Architect with Crunchy Data. My husband and I moved to a small village in the French Alps 17+ years ago because of our love of mountain biking (Essex isn’t exactly well-known for its mountains).

PostgreSQL Europe strongly believes in making PGConf.EU 2022 available to everyone in our community, and as part of that effort we are proud to offer childcare for children ages 3–15 to parents attending PGConf.EU 2022.

History

PostgreSQL supports two types of JSON implementations: JSON and JSONB. The first implementation of JSON has been released in PostgreSQL 9.2 in 2012. JSONB has been added two years later in PostgreSQL 9.4.

There are still two JSON standards, that differ. One is RFC7159 by Douglas Crockford. The other one the ECMA 404.

It is possible to install and configure Pgpool-II in EC2 instances. However, the common ways to assign VIP can't be used in the Cloud. We need to consider alternatives for assigning VIP in the Cloud.

This post describes how to configure and manage VIP in AWS.

There several ways to configure VIP in AWS:

The PostGIS Team is pleased to release PostGIS 3.3.1.

This is a bug fix release to address an issue compiling against PostgreSQL 15 Beta 4.

Best served with PostgreSQL 15 Beta 4.

serial is a popular pseudo data type in PostgreSQL which is often used to generate auto-increment columns. However, this can lead to issues which are often underestimated. So what is the problem? Some of you might have already seen the following error message in real life:

This is a technical investigation into memory allocation at the PostgreSQL and linux (memory allocation/malloc()) levels. Any comments are welcomed!

PostgreSQL Person of the Week Interview with Jeevan Ladhe: My name is Jeevan Ladhe. I live in Maharashtra state of India, in Pune city. I stay here with my mother, wife and son. My older brother and his family, who are dearer to us, stay in the same state in the city well known as Mumbai.

The amount of configuration parameters have grown a lot since when I started using PostgreSQL. With PostgeSQL 14, the current version at the time writing, there are currently 346 parameters, that can be configured.

Most of the time it is unnecessary to touch most of them. On the other hand, the default configuration is anything but usable for nearly anything, except en embedded environment.

Looking At Configuration Parameters

This can easily be solved with SQLl:

First off - :wave: heya old friends, it’s been a while! After a slight “busy-with-other-things” hiatus (changing jobs, genome multiplication) I thought it’s about time to hit the keyboard again to avoid becoming overly “rusty” with writing and also to help my ageing brain in future as it’s pretty neat...

After working with PostgreSQL for so many years it’s sometimes surprising to see some of the utilities, to a certain degree, have capabilities that remain relatively unknown to more than a few people. So let me introduce you to manifests.

Back in March and April I wrote couple of blogposts about upcoming new great feature – full SQL/JSON. Unfortunately, as of today SQL/JSON has been reverted (removed from sources), both from development version 16, but also from “almost ready" version 15. There is lengthy discussion about it which you can definitely read if you're so … Continue reading "SQL/JSON is postponed"