I distribute daily [Hivemind database dumps](https://steemit.com/hivemind/@emrebeyler/steps-to-restore-a-hivemind-database-snapshot) in the last 5 months. The format of the dump was traditional in that timeframe. In order to optimize restoring time on fresh installs, I have switched it to the custom dump format.

This format is compressed by default and allows concurrent dump/restore actions. On my tests, rebuilding a fresh Hivemind into the latest head block took me 2.5 hours. (Including the download time.)

[Steps to restore the database](https://steemit.com/hivemind/@emrebeyler/steps-to-restore-a-hivemind-database-snapshot) are the same except the restoring command.

Now, you can restore the database with

***
```
pg_restore -j 8 -U <db_user> -d <db_dump> hive_latest.dump
```
***

`-j` stands for thread count. I have aligned it with my core count in my test.

Also, worth noting that the dump is taken from a PostgreSQL 10.8 server. It may not be compatible with other PostgreSQL versions.