|
35 | 35 | <xref linkend="app-pgdump"/> for this purpose. The basic usage of this |
36 | 36 | command is: |
37 | 37 | <synopsis> |
38 | | -pg_dump <replaceable class="parameter">dbname</replaceable> > <replaceable class="parameter">outfile</replaceable> |
| 38 | +pg_dump <replaceable class="parameter">dbname</replaceable> > <replaceable class="parameter">dumpfile</replaceable> |
39 | 39 | </synopsis> |
40 | 40 | As you see, <application>pg_dump</application> writes its result to the |
41 | 41 | standard output. We will see below how this can be useful. |
@@ -109,9 +109,9 @@ pg_dump <replaceable class="parameter">dbname</replaceable> > <replaceable cl |
109 | 109 | be read in by the <application>psql</application> program. The |
110 | 110 | general command form to restore a dump is |
111 | 111 | <synopsis> |
112 | | -psql <replaceable class="parameter">dbname</replaceable> < <replaceable class="parameter">infile</replaceable> |
| 112 | +psql <replaceable class="parameter">dbname</replaceable> < <replaceable class="parameter">dumpfile</replaceable> |
113 | 113 | </synopsis> |
114 | | - where <replaceable class="parameter">infile</replaceable> is the |
| 114 | + where <replaceable class="parameter">dumpfile</replaceable> is the |
115 | 115 | file output by the <application>pg_dump</application> command. The database <replaceable |
116 | 116 | class="parameter">dbname</replaceable> will not be created by this |
117 | 117 | command, so you must create it yourself from <literal>template0</literal> |
@@ -141,7 +141,7 @@ psql <replaceable class="parameter">dbname</replaceable> < <replaceable class |
141 | 141 | behavior and have <application>psql</application> exit with an |
142 | 142 | exit status of 3 if an SQL error occurs: |
143 | 143 | <programlisting> |
144 | | -psql --set ON_ERROR_STOP=on dbname <infile |
| 144 | +psql --set ON_ERROR_STOP=on dbname <dumpfile |
145 | 145 | </programlisting> |
146 | 146 | Either way, you will only have a partially restored database. |
147 | 147 | Alternatively, you can specify that the whole dump should be |
@@ -201,11 +201,11 @@ pg_dump -h <replaceable>host1</replaceable> <replaceable>dbname</replaceable> | |
201 | 201 | cluster, and also preserves cluster-wide data such as role and |
202 | 202 | tablespace definitions. The basic usage of this command is: |
203 | 203 | <synopsis> |
204 | | -pg_dumpall > <replaceable>outfile</replaceable> |
| 204 | +pg_dumpall > <replaceable>dumpfile</replaceable> |
205 | 205 | </synopsis> |
206 | 206 | The resulting dump can be restored with <application>psql</application>: |
207 | 207 | <synopsis> |
208 | | -psql -f <replaceable class="parameter">infile</replaceable> postgres |
| 208 | +psql -f <replaceable class="parameter">dumpfile</replaceable> postgres |
209 | 209 | </synopsis> |
210 | 210 | (Actually, you can specify any existing database name to start from, |
211 | 211 | but if you are loading into an empty cluster then <literal>postgres</literal> |
|