Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 647
    • Issues 647
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #3031
Closed
Open
Issue created Dec 24, 2022 by debula@debula

pg_restore is slow after creating index "public.activities_visibility_index"

Follow-up to #3030 (closed).

I've moved to another server before and the restore process was fast.

Today I want to restore from an archive file that is less than 200MB:

sudo -Hu postgres pg_restore -d pleroma -v -1 /var/lib/postgresql/pleroma.pgdump

At first, everything worked fine, but after the creation of index "public.activities_visibility_index", hours passed and no new messages appeared.

Full log: pg_restore.txt

I don't understand what pg_restore is doing, and from the log file it looks like it's restoring the activities table, but it's stuck.

Edited Dec 24, 2022 by debula
Assignee
Assign to
Time tracking