_Rho_

This movie looks so stupid. I'm 100% going to see it.

This is fascinating

My biggest takeaway from reading through the GitHub comments though is that it seems like no one actually knows where much of the SQL comes from? As in it's possible that the bug in question is just one manifestation of old, handwritten Postres code that may or may not be optimized (Or even logical?).

I don't mean this in a critical way, as things like this are bound to happen in an open-source, federated world. However, I would think a comprehensive audit of the Lemmy Postgres triggers, queries, etc could potentially save us all from some future headaches.

You had me in the first half, not gonna lie.

"They do so by breaking the law in multiple countries and further contributing to a system where creators don't get paid!"

Reminds me of the Walt Disney ERB lines:

"I'm the Disney landlord of your intellectual property"

You seriously made a post just to say Meg Ryan was Beautiful?

Upvotes

r/oddlyspecific. Wait... Wrong site.

Moving more processes to be asynchronous make sense. As that's also how Reddit's backend works.

Sort of an unrelated question, but are Lemmy instances specifically designed to work on top of Postgres? Or could they technically use "any" database?

UNO, but it's a Yu-Gi-Oh style anime movie.

As a data engineer, I'd be interested in hearing more about the SQL troubleshooting.

EDIT: It looks like !lemmyperformance@lemmy.ml is a good place to subscribe to for more technical info on some of these performance improvements.

Also the Lemmy GitHub of course contains more information on bugs/enhancements/etc.

I had hoped the reviews would be more positive. But it sounds like people still enjoyed it. And I mean, I'm going to see it either way.

That will never wor-

Likes

Comments

Shares

Subscribes

Donates

Favorites

Reports

Bruce banner: "See that's the secret... It's always bean day"