If you write queries – and forgive me, because I know that sounds like everyone, and that’s because it is – then you need to know how Postgres handles nulls. There are only two kinds of developers: the ones who memorized how nulls work, and the ones with incorrect query results.
If you wanna know how Amazon Aurora is different from regular Postgres, check out this one-hour re:Invent session video. That link jumps to about 10 minutes into the session because most of the first 10 minutes doesn’t have slides, and the point where I linked into is a good starting point if you’re just focused on Postgres.
If your query isn’t using indexes, but the indexes are right there, you might consider Shayon Mukherjee’s tactic of lowering the random_page_cost setting to encourage the optimizer to use indexes.
Video of the Week:
PostgreSQL@SCaLE
The PostgreSQL @SCaLE was a 2-day, multi-track event on March 14-15 in Pasadena, California. Here are the talks:
- A Look at the Elephant’s Trunk: PostgreSQL 17 by Magnus Hagander
- Collation Challenges: Sorting It Out by Joe Conway
- Database Schema Management for Lazybones: From Chaos to Heaven by Julien Riou
- Even Children Can Work with Postgres by Tatiana Krupenya
- JSON and Analytics inPostgres Using Index and Columnar by Gleb Otochkin
- Leveraging PrestoDB for Data Success by Kiersten Stokes
- PostgreSQL Performance for Application Developers by Umair Shahid
- Securing Your PostgreSQL Data: A Comprehensive Guide to Protecting Your Database Assets by Hettie Dombrovskaya
- Recovering from Data Loss Despite Not Having a Backup by Jimmy Angelakos
- Testing Your PostgreSQL Backups: A Practical Guide by Nick Meyer
- Transforming Data with the Power of PostgreSQL and SQL by Ryan Booz
- Vectors are the New JSON by Jonathan Katz