Looks like a nice kit to add to your tool belt. Does some handy checks if you have a Postgres database to manage.

Indeed, in most case you don't need the extra complexity. Also interesting is showing that even if the application has to scale rapidly you still got quite some time to plan the transition to something else. It makes Postgres a sane default choice.

This article is short but very interesting. That's indeed something to keep in mind when using Postgres, you could have surprisingly bad performance results in some cases otherwise.

Indeed they did plan ahead very well. It's no surprise if Postgres is doing so well this days.

Wow, this was a really bad index corruption indeed.

It shows unexpected results in its measurements. It also highlights the importance of proper settings for your database system.

A nice extension for Postgres allowing to ease the protection of personal information.

I definitely like the approach of having vectorisation in the RDBMS directly. This is one less moving part, less complexity at the application level to synchronize everything together. In this case it's a Postgres extension.

Since everything has design choices which imply trade offs. Here is the main issue with PostgreSQL right now. Hopefully it'll get modernized at some point.

Need to duplicate data in Postgres? Several options are on the table.

Looks like an interesting tool for creating anonymized pre-production environments.

Definitely not as simple as it sounds. The devil is once again in the details.

Nice return on experience of using a simple stack to serve loads of web requests.

Interesting use of database templates and memory disks to greatly speed up test executions.

Nice exploration of the GitLab database schema. This highlights and finds quite a few of the choices made with an eye on performances.

Nice index pointing to resources to do many things with Postgres.

Ever wondered how to programmatically introspect query plans? This is a long article but good starting point on how it's represented under the hood.

This is a very important point. Communities should make sure that new blood gets in. Companies should also avoid just recruiting top talent and groom juniors to contribute.

Good primer about database transactions and the issues you might run with when using them.

Excellent points. Don't be fooled by alluring architecture changes. Always keep the complexity in check and favor tuning what's already here or changing your use patterns to meet the performance you need.