Postgresql

Welcome to show 3 for PG Down Under!

Once again, I really enjoyed recording today’s show. It features Ryan Booz. Ryan is an evangelist with our friends at Red-Gate, focussing on PostgreSQL.

In this show, Ryan shares his experiences with community in relation to PostgreSQL. Next, we ventured into the challenges and benefits of being an application vendor working against PostgreSQL, and in particular, the extensibility model and how it compares to other products.

2024-07-25

Welcome to show 2 for PG Down Under!

I really enjoyed recording today’s show with John Miner. John is a data architect at Insight in the USA. Over many years, John was a data platform MVP, is a strong community contributor, and blogs at craftydba.com.

After I created the Wide World Importers sample databases for Microsoft back in 2016, I did also do a migration of the code to PostgreSQL. That didn’t get released for quite a while but I’ve now seen it out there in the wild. I wanted to do a show on the migration but was concerned that I had done it so long ago, that I might have forgotten what surprised me at the time.

2024-05-04

Welcome to PG Down Under!

I’ve worked with data most of my life and I love all aspects of it, and PostgreSQL has been part of it. Whenever possible, I’ve attended local PostgreSQL user groups to make sure I stay across what’s happening with it, even though my primary work was with SQL Server. PostgreSQL has been part of many client engagements over the years.

For some time, I’ve been starting to build up a series of podcasts for PostgreSQL developers and DBAs.

2024-03-08

The link below is to quite a fascinating article that on the surface is about why Uber moved to MySQL from PostgreSQL.

https://use-the-index-luke.com/blog/2016-07-29/on-ubers-choice-of-databases

What it really is about is a limitation in how PostgreSQL indexes are updated. They consider it a severe limitation.

With SQL Server (and MySQL), if you update a few columns in a row, only the indexes that have that column are updated. In PostgreSQL, all indexes still need to be updated. I understand why they’ve done that but I can see why users might not want that behavior.

2016-08-04