1
23
submitted 1 month ago by [email protected] to c/[email protected]
2
14
submitted 2 months ago by [email protected] to c/[email protected]
3
4
submitted 2 months ago by [email protected] to c/[email protected]
4
18
submitted 3 months ago by [email protected] to c/[email protected]
5
6
submitted 3 months ago by [email protected] to c/[email protected]

Prolog language for PostgreSQL

This is a PostgreSQL extension that allows writing stored procedures in Prolog.

This embeds Scryer Prolog into a PostgreSQL extension.

Proof of concept! Not ready for any actual use.

6
75
submitted 3 months ago by [email protected] to c/[email protected]

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

7
11
submitted 3 months ago by [email protected] to c/[email protected]
8
7
submitted 3 months ago by [email protected] to c/[email protected]
9
6
submitted 3 months ago by [email protected] to c/[email protected]
10
8
submitted 3 months ago by [email protected] to c/[email protected]
11
10
submitted 3 months ago by [email protected] to c/[email protected]
12
32
submitted 4 months ago by [email protected] to c/[email protected]

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?

13
10
submitted 4 months ago by [email protected] to c/[email protected]
14
5
submitted 4 months ago* (last edited 4 months ago) by [email protected] to c/[email protected]

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

15
9
UUID Benchmark War (ardentperf.com)
submitted 5 months ago by [email protected] to c/[email protected]
16
8
submitted 5 months ago by [email protected] to c/[email protected]
17
27
submitted 5 months ago by [email protected] to c/[email protected]
18
7
submitted 5 months ago by [email protected] to c/[email protected]
19
9
submitted 5 months ago by [email protected] to c/[email protected]
20
19
submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]

GDS is leading the digital transformation of the UK government.

21
5
submitted 5 months ago by [email protected] to c/[email protected]

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.

22
29
Don't Do This - PostgreSQL wiki (wiki.postgresql.org)
submitted 5 months ago by [email protected] to c/[email protected]
23
15
submitted 5 months ago by [email protected] to c/[email protected]
24
4
submitted 5 months ago by [email protected] to c/[email protected]

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"

25
11
submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]
view more: next ›

PostgreSQL

612 readers
1 users here now

The world's most advanced open source relational database

Project
Events
Podcasts
Related Fediverse communities

founded 1 year ago
MODERATORS