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

Via https://botsin.space/@planetpostgresql/111602978945432365

PGDay Chicago is a non–profit, community–run conference series in the United States focused on PostgreSQL, the world’s leading open source database. Our conference delivers one day packed with presentations about PostgreSQL and related technologies and the usual hallway and social track. Our conference will be held April 26th, 2024, in Chicago, IL.

A managed Postgres offering developed by Supabase and Fly.io