Neues vom PostgreSQL Planet
Just a quick note to highlight some bug fixes and improvements in the pgxn/pgxn-tools Docker image in the last few weeks.
This month's PgSQLPhriday #015 topic is about UUIDs. Lætitia Avrot is this month's host, see her post for the full challenge text. The topic is described as a debate between the Database People and Developers. I'm not sure there's such a clean divide on people's opinions on the topic, as I know plenty of Database People that have settled on using UUIDs as their default. Similarly, I know even more developer types that have followed the arguably more conventional choice of using an auto-incrementing ID.
At PostGIS Day 2023, one of our speakers showed off a really cool demo for getting JSON and SVGs in and out of Postgres / PostGIS and into Google Sheets. Brian Timoney put together several open source projects in such a cool way that I just had to try it myself. If you want to see his demo video, it is on YouTube.
As in previous years, I've pulled together a few statistics on code contributions to PostgreSQL. See previous posts in this series for methodology and caveats. I calculate that, in 2023, there were 221 people who were the principal author of at least one PostgreSQL commit. 66% of the new lines of code were contributed by one of 18 people, and 90% of the new lines of code were contributed by one of 50 people. Here they are. Asterisks indicate non-committers.
Something strange I discovered while using DBIx::Class and DBI.‘generated always as identity’ columns do not have default values (or do they?)
PostgreSQL has two ways of defining what other databases call an auto-increment column:
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.
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.
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.
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.
Umair Shahid: “But how much does a PostgreSQL license actually cost?” A Frequently Asked Question from Oracle users considering PostgreSQL
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 […]
I was recently conducting a training session on the query planner, looking at the bits of information, and we discussed the “Rows Removed by Filter.”
I was seeing a value of one less than the total row count, which made sense, since the query had a LIMIT of 1.
However, as I changed the query parameter, the value from “Rows Removed by Filter” returned different values. I realized I didn’t fully understand the behavior, so I wanted to take that opportunity to strengthen my understanding of what was happening.
The PostgreSQL Project is present with a booth at FOSDEM ever since 2007. And ever since 2008 we organize a Devroom, starting 2013 we also have our own PGDay on the Friday before FOSDEM. This year it’s the 10th FOSDEM PGDay, skipping 2021 and 2022 for obvious reasons.
This blog post provides useful information for visitors of the PGDay, the booth and the PostgreSQL Devroom at FOSDEM.