A weapon of ass-destruction?

My wife was thinking I was hacking while I was troubleshooting my VPS. She is way more educated than I am. She loves watching CSI, so that’s probably why she thought that.

Oh god. When a great Dane shakes it’s head, the drool gets launched everywhere. I’ve seen it on the ceiling in some cases. I would never get a dog with drool flaps.

Jesus. That’s ridiculous!

She doesn’t do it for me either, but in no world is this woman average. She is definitely objectively beautiful. Just not my jam.

If a server has a bot set up on lemmy federate, the server is automatically loading posts for the community. Especially handy for smaller instances where none of the users on there have noticed the post, or have subscribed.

Since lemmy is still relatively small, a lot of people don’t subscribe, and instead use the all feed, and maybe even block communities that don’t interest them.

Dance monkey. How dare you not know the alphabet back to front?

Who cares. They are killing anything in their sight. Fuck them.

The instigator is different. Not trying to condone Israel, but the initial reason for invading is different.

Fuck both Russia and Israel.

Well that would do it. Thanks for pointing out!

It thankfully seems to have been fixed thanks to @graycube@lemmy.world. Running analyze verbose; in postgres.

The pgautoupgrade was added for the new version because this deployment is an all-in-one solution for running lemmy. And upgrading the databases turned out to be quite the effort until some user pointed the maintainer towards pgautoupgrade here.

I tried running lemmy before I found out about this, but this just makes it so much more convenient to run.

Thanks. I ran it. Hopefully it’ll make a difference.

Edit: It looks like this did the trick. I’ll keep monitoring to see if it sticks. Thanks again!

I think so. I have lemmy and everything needed running through a single docker container using Lemmy-Easy-Deploy.

I added pg_stat_statements, and ran it. This was the result:

# SELECT count(*) FROM pg_stat_activity;
 count
-------
    11
(1 row)

ERROR:  extension "pg_stats_statements" is not available

Even though it’s added in the customPostgresql.conf shared_preload_libraries = 'auto_explain,pg_stat_statements'

ERROR:  extension "pg_stats_statements" is not available

Even though it’s added in the customPostgresql.conf shared_preload_libraries = 'auto_explain,pg_stat_statements'

I have. And I tried to tweak it with no avail. But it was working within acceptable levels before the update.

deleted by creator

I have. It’s running postgres v16.3

Aaaaaaaaah! NEIN!