Neues vom PostgreSQL Planet

I'm happy to present our new product, Postgres.AI Bot. It is powered by OpenAI's GPT-4 Turbo and is designed to help engineers improve their experience when working with PostgreSQL. This bot has a vast knowledge base with over 110,000 entries, including documentation, source code for different PostgreSQL versions, and related software like PgBouncer, Patroni, and pgvector. It also integrates expert articles and blogs.

Today, I’m very proud and honored to host for the second time the great monthly PGSQL Phriday event! It’s sometimes difficult to find a great topic and I like the kind of topics where there is no consensus. This one is a little particular: in my humble opinion, the database community has a consensus, it’s that developers don’t agree.` Let’s organize a debate between database people and developers! I hope this will lead to great conversation and better understanding between those two groups!

Me and Enrico talk about out latest book on Doug’s Tech Bit show!

Learn PostgreSQL - second edition - Tech Bits

I’m really glad that me and Enrico were hosted on the great Doug’s Tech Bits show. You can see the podcast on YouTube:

I would like to thank Doug Ortiz for his excellent work.

Introduction

When you send a query to PostgreSQL, it will undergo several processing stages in the backend. Each of these stages has different responsibilities to ensure that you receive correct responses in shortest amount of time possible. Yes, they can be quite large and complex to fully understand but I believe it is important for PostgreSQL developer like you to at least understand their roles in handling a query. In this blog, I will give an overview of each query processing stage, their roles and significance in PostgreSQL architecture.

Google Summer of Code is back for 2024! Please review this announcement blog post.

And please make yourself familiar with the GSoC 2024 timeline!

A commit caught my attention during my technical watch:

At Tembo (like every aaS provider), we wanted to have a customer data warehouse to track and understand customer usage and behavior. We wanted to quickly answer questions like "How many Postgres instances have we deployed?", "Who is our most active customer?" and "How many signups do we have by time?". In order to do this, we needed to bring data from several sources into a single location and keep it up-to-date so we could build the dashboards.

Unraveling the Mystery: Why PostgreSQL Costs You Nothing  Each time I mention that PostgreSQL comes with zero licensing fees, I’m met with skeptical looks and a barrage of “Really? But how much does the license actually cost?”. It has happened enough times that I decided to write a blog explaining this, keeping in mind especially […]