I've used many times this technique for transferring databases between servers:
pg_dump --no-owner -Fd mydb -j 4 -f tmp/mydb scp -r tmp/mydb otherserver:tmp/
then in the other server:
dropdb --if-exists mydb && createdb -T template0 mydb && pg_restore -j 4 -d mydb tmp/mydb && rm -rf tmp/mydb
It has worked flawlessly. Using Postgres 9.3.16 and CentOS 7.
But now, in a new server, pg_restore complains:
pg_restore: [archiver] parallel restore is not supported with this archive file format
I could remove the
-j 4 parameter, but theorically it should be valid.
According to the pg_restore doc:
-j number-of-jobs --jobs=number-of-jobs
Run the most time-consuming parts of pg_restore — those which load data, create indexes, or create constraints — using multiple concurrent jobs. This option can dramatically reduce the time to restore a large database to a server running on a multiprocessor machine.
Each job is one process or one thread, depending on the operating system, and uses a separate connection to the server.
The optimal value for this option depends on the hardware setup of the server, of the client, and of the network. Factors include the number of CPU cores and the disk setup. A good place to start is the number of CPU cores on the server, but values larger than that can also lead to faster restore times in many cases. Of course, values that are too high will lead to decreased performance because of thrashing.
Only the custom and directory archive formats are supported with this option. The input must be a regular file or directory (not, for example, a pipe). This option is ignored when emitting a script rather than connecting directly to a database server. Also, multiple jobs cannot be used together with the option --single-transaction.
I'm using the directory format in
Why does it complain?