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