operators should be used to redirect it into a file.
-
-
Options
-
pg_dumpall accepts the following
- command line arguments:
+
pg_dumpall will need to connect several times to the
+
PostgreSQL server, asking for the password each
+ time. It will probably be very convenient to have a PGPASSWORDFILE in that case.
+
+
+
+
+
+
Options
-
-
- -c, --clean
-
+
pg_dumpall accepts the following
+ command line arguments:
+
+
+
+ -c, --clean
+
Include SQL commands to clean (drop) database objects before
recreating them. (This option is fairly useless, since the
output script expects to create the databases themselves;
they would always be empty upon creation.)
-
-
-
-
-
- -g, --globals-only
-
+
+
+
+
+
+ -g, --globals-only
+
Only dump global objects (users and groups), no databases.
-
-
-
-
-
- -h host
-
+
+
+
+
+
+ -h host
+
Specifies the host name of the machine on which the database
server is running. If host begins with a slash, it is used as
the directory for the Unix domain socket. The default is
taken from the PGHOST environment variable, if
set, else a Unix domain socket connection is attempted.
-
-
-
-
-
- -p port
-
+
+
+
+
+
+ -p port
+
The port number on which the server is listening. Defaults to
the PGPORT environment variable, if set, or a
compiled-in default.
-
-
-
-
-
- -U username
-
+
+
+
+
+
+ -U username
+
Connect as the given user.
-
-
-
-
-
- -W
-
+
+
+
+
+
+ -W
+
Force a password prompt. This should happen automatically if
the server requires password authentication.
-
-
-
-
-
+
+
+
+
+
Any other command line parameters are passed to the underlying
calls. This is useful to control some aspects of the output
format, but some options such as ,
,
, and
class="parameter">dbname should be avoided.
-
-
+
settings and environment variables available to
psql
and the
libpq front-end library do apply.
+
+
+
vacuumdb will need to connect several times to the
+
PostgreSQL server, asking for the password each
+ time. It will probably be very convenient to have a PGPASSWORDFILE in that case.
+
+