sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-31 00:03:57 -04:00
Code Issues Projects Releases Wiki Activity

Document pg_restore --jobs as a performance enhancement.

Browse Source
This commit is contained in:
Bruce Momjian 2010-02-26 02:31:52 +00:00
parent 4f96ddd1d3
commit ca8e3a51a0
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/perform.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/perform.sgml,v 1.73 2010/01/15 09:18:59 heikki Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/perform.sgml,v 1.74 2010/02/26 02:31:52 momjian Exp $ -->
<chapter id="performance-tips">
<title>Performance Tips</title>
@ -1027,7 +1027,10 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
possibly discarding many hours of processing. Depending on how
interrelated the data is, that might seem preferable to manual cleanup,
or not. <command>COPY</> commands will run fastest if you use a single
transaction and have WAL archiving turned off.
transaction and have WAL archiving turned off.
<application>pg_restore</> also has a <option>--jobs</> option
which allows concurrent data loading and index creation, and has
the performance advantages of doing COPY in a single transaction.
</para>
</listitem>
<listitem>