From 775f1b379e3a282140f60ef65a11d1444dc80ccf Mon Sep 17 00:00:00 2001 From: Andrew Dunstan Date: Mon, 2 Feb 2009 20:07:37 +0000 Subject: Provide for parallel restoration from a custom format archive. Each data and post-data step is run in a separate worker child (a thread on Windows, a child process elsewhere) up to the concurrent number specified by the new pg_restore command-line --multi-thread | -m switch. Andrew Dunstan, with some editing by Tom Lane. --- doc/src/sgml/ref/pg_restore.sgml | 24 +++++++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index f13c6447722..92c9f4be935 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -1,4 +1,4 @@ - + @@ -241,6 +241,28 @@ + + + + + + Run the most time-consuming parts of pg_restore + — those which load data, create indexes, or create + constraints — using multiple concurrent connections to the + database. This option can dramatically reduce the time to restore a + large database to a server running on a multi-processor machine. + + + + This option is ignored when emitting a script rather than connecting + directly to a database server. Multiple threads cannot be used + together with . Also, the input + must be a plain file (not, for example, a pipe), and at present only + the custom archive format is supported. + + + + -- cgit v1.2.3