Conversation

Notices

1. Embed this notice
   Sexy Moon (moon@shitposter.club)'s status on Thursday, 15-Sep-2022 01:35:16 JST Sexy Moon
   Restore from backup has been tested. A full restore of SPC's database to SSD would take almost 10 hours.
   • Hélène likes this.
   • Embed this notice
     anime graf mays ?️? (graf@poa.st)'s status on Thursday, 15-Sep-2022 01:39:03 JST anime graf mays ?️?

     in reply to

     @Moon i too almost fell for that, and poast was down 7 hours because of that. using -j 48 i restored poasts in about 42 minutes after i realized because it was a custom backup that i could do that

     Alex Gleason likes this.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Thursday, 15-Sep-2022 01:40:11 JST Alex Gleason

     in reply to

     • anime graf mays ?️?
     Didn't you also restore the full schema before the data?
   • Embed this notice
     anime graf mays ?️? (graf@poa.st)'s status on Thursday, 15-Sep-2022 01:43:20 JST anime graf mays ?️?

     in reply to

     • Alex Gleason

     @alex @Moon nope I tried that and it errored out trying to restore several tables because of foreign key constraints. i dropped that plan altogether for just straight pg_restore -d <pleroma_db> -v -j 48 pleroma.dump and it worked first shot

     Alex Gleason likes this.
   • Embed this notice
     pwm (pwm@poa.st)'s status on Thursday, 15-Sep-2022 02:06:55 JST pwm

     in reply to

     • anime graf mays ?️?
     • Alex Gleason
     • Moon
     @alex @Moon @moon gonna reply here but what you are supposed to do is create the schema without constraints, import the data, and then create the constraints. pg_dump does this for you, but that's the manual process should you need it. Possibly why @graf and @moon were getting constraint errors when they loaded schema first
     Alex Gleason likes this.