![](https://aussie.zone/pictrs/image/2644a4fe-cce3-4126-b80b-40e6369976d1.jpeg)
![](https://lemmy.nz/pictrs/image/9678c79e-3540-4e48-aa01-0d282dfcaeac.png)
The biggest gotcha with 0.19.4, is the required upgrades to postgres and pictrs. Postgres requires a full DB dump, delete, recreate. Pict-rs requires its own backend DB migration, which can take quite a bit of time.
I also have backup accounts on these instances:
https://beehaw.org/u/lodion
https://sh.itjust.works/u/lodion
https://lemmy.world/u/lodion
https://lemm.ee/u/lodion
https://reddthat.com/u/lodion
The biggest gotcha with 0.19.4, is the required upgrades to postgres and pictrs. Postgres requires a full DB dump, delete, recreate. Pict-rs requires its own backend DB migration, which can take quite a bit of time.
It was removed deliberately during the reddit exodus in order to direct new Lemmy users elsewhere. Rather than to overload lemmy.ml further.
Hey I do exactly the same, high 5!
The kiwi’s have spun something up over here
I’m far too disorganised to coordinate that. Though I’m sure someone from /c/Melbourne will 🙂
The largest table holds data that is only needed by Lemmy briefly. There is a scheduled job to clear it… Every 6 months. There are active discussions on how best to handle this.
On my instance I’ve set a cronjob to delete everything but the most recent 100k rows of that table every hour.
By the way, upgradding to lemmy version 0.18.1 is well worth it. Some massive under the hood performance improvements 🙂
Mate, that sounds like an awesome night. I’d call that a win!
Your mum was a programmer in the 60s? She must be incredibly in so many ways!
Ok yeah, I guess for external links direct to images it makes sense for the image to be retrieved by each instance. Still, its not intuitive behaviour and it doesn’t seem to be widely understood at all.
Thanks for reporting back.
Yeah, I’ve gone over 24 hours now without it occurring… but not calling it “fixed” until at least a week.
I’ve been seeing similar since upgrading to 0.18. Upgraded to 0.18.1-rc.9 yesterday… haven’t seen it reoccur again… yet.
Here is an example I happened to be at my PC for:
I wish I knew… I’ve seen the behavior you’ve described, but others tell me it doesn’t happen.
Streaming providers are known to have different bitrates in different regions.
I wanted an instance specifically for Australians… so I made one 😀
Your instance must be very new, very few users, very inactive… or all of the above. I stood up aussie.zone just under a month ago, Postgres DB is currently 9.6GB.
Yep, that is nearly but not always the case.
Nope… thats what I’m talking about… image posts to remote communities, with the images being sourced from my instance. Like I said, next time I spot it I’ll dig into it further.
What software is your instance running?
Hey Dave, yeah I know about the issues with high latency federation. Have been in touch with Nothing4You, but not discussed the batching solution.
Yes losing LW content isn’t great… but I don’t really have the time to invest to implement a work around. I’m confident the lemmy devs will have a solution at some point… hopefully when they do the LW admins upgrade pronto 🙂