PostgreSQL maintainer Simon Riggs has died in a small airplane crash, on Tuesday.

For those who didn't know Simon, he's responsible for PostgreSQL Binary Replication and many big data features. He and I worked together at Greenplum 2006-2008. Postgres would not be the world-leading DB it is today if it weren't for him.

https://www.bbc.com/news/articles/cjex992z0wlo

Lemmy currently uses distinct tables like post_like: (post_id, person_id, score) and post_saved. Unfortunately this causes performance issues when we have to join many of these tables to create views.

One suggestion in this PR, is to combine these into a single post_action table, with a lot of optional columns depending on the action. This solution scares me a little, because I'm afraid we might lose data integrity, and many of our constraints with so many optional columns.

Is there a better way of doing this in SQL?

Is it possible to upgrade PostreSQL from 14 to 16 directly when using containers?
@postgresql

GDS is leading the digital transformation of the UK government.

We walk through the incremental backup feature committed to the Postgres 17 development branch by Robert Haas. We show an example on our local machine.

Via https://mstdn.social/@michristofides/111738621686733546

There's a fun looking new weekly #PostgreSQL newsletter from Brent Ozar (one of my favourite authors from the SQL Server community).

From this week's post: "But… I’m a DBA, and you know what DBA stands for: Doesn’t Believe Anyone"

via https://fosstodon.org/@adamchainz/111694569833742858