Neues vom PostgreSQL Planet

This is a short announcement of a new PostgreSQL wiki page called Operations cheat sheet . I curated many useful pages (that I find so), mostly from blogs registered in Planet PostgreSQL . Also, I summarized some topics for quick reference. I created this page so that users can learn from rich wisdom PostgreSQL community people and get ready for troubleshooting. For details, please see the Introduction section.

Vector search in Postgres is a space that has seen very active development in the last few months. While Pgvector is known to most people, a few weeks ago we came across Lantern, which also builds a Postgres-based vector database. So, we thought about benchmarking both to compare the two approaches. In this post, we'll cover:

A short recap on some issues when dealing with PL/Java and Rocky Linux.

Installing PL/Java on PostgreSQL 16 and Rocky Linux

It has been a while since I last used PL/Java, and that’s mostly due to the fact that I (luckily) use much more Perl (and hence, PL/Perl) in my everyday activity than Java.

In PostgreSQL, functions and procedures can be written in many different programming languages including but not limited to PL/pgSQL, PL/Perl, PL/Python and a lot more. This flexibility gives the end user the choice to write code in languages of their choice. However, this flexibility has some implications which are often forgotten. Loading libraries early is one of them.

• Background
• Password Encryption (i.e.

Introduction

In this blog, we’ll go over PostgreSQL’s implementation and handling of JSON objects. Having some experience with Linux, Postgres, and JSON is necessary as we’ll not only be going over these new features but also how to implement them. This blog was written using PostgreSQL 16 (Development Version) running on Ubuntu 23.04. First I’ll go over some background on JSON as a short refresher, then move on to how we use JSON in Postgres, followed by what helpful functions we can use to interact with JSON objects.

On 4th of January 2024, Peter Eisentraut committed patch: ALTER TABLE command to change generation expression   This adds a new ALTER TABLE subcommand ALTER COLUMN ... SET EXPRESSION that changes the generation expression of a generated column.   The syntax is not standard but was adapted from other SQL implementations.

You may have noticed a file called postmaster.pid inside your data directory. This file gets created when Postgres first starts up, and gets removed on a clean shutdown. It seems to contain some random numbers and strings, but what do they all mean?

The file will look like this:

2757 /home/greg/pg/17/data 176540940 5432 /tmp * 8675309 12 ready

Here is a quick cheat sheet of the contents:

Today was the day - our PostgreSQL Query Optimization book was published! The book is currently available on Apress website, and if you are interested in the paper book, I believe that’s the fastest way to get it.

The November commitfest is ripe with new interesting features! Without further ado, let’s proceed with the review.

If you missed our July and September commitfest reviews, you can check them out here: 2023-07, 2023-09.

The PGConf.dev CFP closes on Monday, January 15 at 11:59pm PST, so if you want to speak at the inaugural PGConf.dev, submit a proposal!

PGConf.dev is the new PostgreSQL Development Conference, the successor to PGCon, a Postgres contribution-focused conference that took place every year in Ottawa. Pronounced "Pee-gee-conf-dot-dev", the inaugural year of PGConf.dev will take place in beautiful Vancouver, Canada, on May 28-31, 2024—with many of the same conference features that made PGCon so great:

Parsing SQL queries and turning them into a syntax tree is not a simple task. Especially when you want to support special syntax that is specific to a particular database engine, like Postgres. And when you’re working with queries day in day out, like we do at pganalyze, understanding the actual intent of a query, which tables it scans, which columns it filters on, and such, is essential. Almost 10 years ago, we determined that in order to create the best product for monitoring and optimizing…

The Cloud is here

There is no getting around “The Cloud”. We all know it, everybody is doing it!
And, let’s face it, if you are looking to get away from the hardship of having to go through troublesome and boring processes to get a new server or a new rack installed in your data center, this might help.

Understand the components involved in logical replication, how it differentiates from streaming replication and the factors to consider.

The post Logical Replication in PostgreSQL appeared first on Stormatics.

2023 was the year of Artificial Intelligence (AI). A lot of companies are thinking about how they can improve user experience with AI, and the most usual first step is to use company data (internal docs, ticketing systems, etc.) to answer customer questions faster and (or) automatically.In this blog post, we will explain the basic […]

As of this writing, I know of three ways to make use of the incremental backup feature that I committed near the end of last month. I'll be interested to see how people deploy in practice. The first idea is to replace some of the full backups you're currently doing with incremental backups, saving backup time and network transfer.

Learn about our approach to connecting multiple nodes in Elixir using Postgres

When I first began exploring how to get involved in the PostgreSQL community, the first event I heard of was PGCon. I was still in college when PGCon had started(!), and I did have FOMO about not going (that said, I don’t think the phrase “FOMO” existed yet).

On 20th of December 2023, Robert Haas committed patch: Add support for incremental backup.   To take an incremental backup, you use the new replication command UPLOAD_MANIFEST to upload the manifest for the prior backup. This prior backup could either be a full backup or another incremental backup. You then use BASE_BACKUP with the INCREMENTAL … Continue reading "Waiting for PostgreSQL 17 – Add support for incremental backup."

You can cut-and-paste the following commands to quickly get a new & clean dev environment for working with PostgreSQL source code. This includes Michael Paquier’s powerful script kit for managing the PostgreSQL development environment.

Setting up from scratch takes me about 5 minutes, plus 3 minutes to configure, compile and install PostgreSQL for testing. Running the full PostgreSQL test suite (including TAP tests) took me 13 minutes.