Conversation

Notices

1. Hoss Delgado (hoss@shitpost.cloud)'s status on Friday, 02-Aug-2024 08:00:22 JST Hoss Delgado

   • 
   • Matty-kun :Christmas_kitty_bell:
   • :btrfly: anime graf mays 🛰️🪐
   • † top dog :pedomustdie:
   • this ad CAN be blocked, bitch
   • Angry Sun
   • pistolero
   • 0

   @mint @kirby @matty @graf @sun @p @0 @dcc Do any of you guys have experience restoring your pleroma database in postgres following the instructions detailed in https://docs-develop.pleroma.social/backend/administration/backup/ ? I've been trying to do a dry run of moving to my new VPS with the postgres dump I made a few days ago and it always hangs at pg_restore: creating INDEX "public.activities_visibility_index" and never completes even if I leave it for a whole day.

   •  (mint@ryona.agency)'s status on Friday, 02-Aug-2024 08:00:22 JST 

     in reply to

     • Matty-kun :Christmas_kitty_bell:
     • :btrfly: anime graf mays 🛰️🪐
     • † top dog :pedomustdie:
     • this ad CAN be blocked, bitch
     • Angry Sun
     • pistolero
     • 0
     @Hoss @dcc @p @kirby @matty @0 @graf @sun Known problem.
     https://blog.freespeechextremist.com/blog/activities-visibility-index-slowness.html
     As a workaround, you can instead dump the schema and data separately, then restore them one after another.
     https://gitlab.com/-/snippets/2228488
     † top dog :pedomustdie: likes this.
   •  (mint@ryona.agency)'s status on Friday, 02-Aug-2024 08:01:11 JST 

     in reply to

     • Matty-kun :Christmas_kitty_bell:
     • :btrfly: anime graf mays 🛰️🪐
     • † top dog :pedomustdie:
     • this ad CAN be blocked, bitch
     • Angry Sun
     • pistolero
     • 0
     @sun @dcc @p @kirby @matty @0 @graf @Hoss It's been merged for ages, and I think it still doesn't help much if you're restoring the DB in one go.
   • Angry Sun (sun@shitposter.world)'s status on Friday, 02-Aug-2024 08:01:12 JST Angry Sun

     in reply to

     • 
     • Matty-kun :Christmas_kitty_bell:
     • :btrfly: anime graf mays 🛰️🪐
     • † top dog :pedomustdie:
     • this ad CAN be blocked, bitch
     • pistolero
     • 0
     @Hoss @dcc @p @kirby @matty @0 @graf @mint I always lose it but p has an index for this that fixes the problem.
   • Hoss Delgado (hoss@shitpost.cloud)'s status on Friday, 02-Aug-2024 08:13:47 JST Hoss Delgado

     in reply to

     • 
     • Matty-kun :Christmas_kitty_bell:
     • :btrfly: anime graf mays 🛰️🪐
     • † top dog :pedomustdie:
     • this ad CAN be blocked, bitch
     • Angry Sun
     • pistolero
     • 0
     I'll give that a try. Follow up question, it's not going to make a difference if I wait to rollback the glussy migrations until after I restore on the new server, right? I just don't want to fuck anything up on the old VPS while we're still using it.
      likes this.
   •  (mint@ryona.agency)'s status on Friday, 02-Aug-2024 08:14:44 JST 

     in reply to

     • Matty-kun :Christmas_kitty_bell:
     • :btrfly: anime graf mays 🛰️🪐
     • † top dog :pedomustdie:
     • this ad CAN be blocked, bitch
     • Angry Sun
     • pistolero
     • 0
     @Hoss @dcc @p @kirby @matty @0 @graf @sun Of course. I think it's a batter course of action since you'll still have an active backup that could be switched back in case you fuck up.
   • this ad CAN be blocked, bitch (kirby@lab.nyanide.com)'s status on Friday, 02-Aug-2024 08:15:50 JST this ad CAN be blocked, bitch

     in reply to

     • 
     • Matty-kun :Christmas_kitty_bell:
     • :btrfly: anime graf mays 🛰️🪐
     • † top dog :pedomustdie:
     • Angry Sun
     • pistolero
     • 0
     @Hoss @dcc @p @matty @0 @graf @mint @sun If you import the db next to a fresh install of pleroma i don't think you can perform the automated rollbacks properly, tried to rollback after i went back to 2.6.3 git commit and it only rolled back one thing rather than many like i was expecting
   •  (mint@ryona.agency)'s status on Friday, 02-Aug-2024 08:15:50 JST 

     in reply to

     • Matty-kun :Christmas_kitty_bell:
     • :btrfly: anime graf mays 🛰️🪐
     • † top dog :pedomustdie:
     • this ad CAN be blocked, bitch
     • Angry Sun
     • pistolero
     • 0
     @kirby @dcc @p @matty @0 @graf @Hoss @sun That migration with rollback you showed me was added months after the last Pleroma source sync in Rebased. Don't make him worry about it.
   • pistolero (p@fsebugoutzone.org)'s status on Friday, 02-Aug-2024 09:26:41 JST pistolero

     in reply to

     • 
     • Matty-kun :Christmas_kitty_bell:
     • :btrfly: anime graf mays 🛰️🪐
     • † top dog :pedomustdie:
     • this ad CAN be blocked, bitch
     • Angry Sun
     • 0
     @mint @sun @0 @Hoss @dcc @graf @kirby @matty
     
     > I think it still doesn't help much if you're restoring the DB in one go.
     
     Yeah, the issue is that the activities_visibility_index is created *before* the AP ID index. Using awk on the dump like the other thing in the post, that works.
      likes this.
   • pistolero (p@fsebugoutzone.org)'s status on Friday, 02-Aug-2024 10:53:24 JST pistolero

     in reply to

     • 
     • Matty-kun :Christmas_kitty_bell:
     • :btrfly: anime graf mays 🛰️🪐
     • † top dog :pedomustdie:
     • this ad CAN be blocked, bitch
     • Angry Sun
     • 0
     @matty @Hoss @dcc @kirby @0 @graf @mint @sun Hey, you still haven't said how you plan to "escalate" and you still haven't "escalated".
     bixnood2.png
     † top dog :pedomustdie: likes this.
   • Matty-kun :Christmas_kitty_bell: (matty@nicecrew.digital)'s status on Friday, 02-Aug-2024 10:53:25 JST Matty-kun :Christmas_kitty_bell:

     in reply to

     • 
     • :btrfly: anime graf mays 🛰️🪐
     • † top dog :pedomustdie:
     • this ad CAN be blocked, bitch
     • Angry Sun
     • pistolero
     • 0

     It will take a long time to do a restoration. Use the jobs flag when restoring, based on the number of processors you have. So, if you have a 4c/8t processor do -j 8 and it should help with the speed, considerably.