fprintf(stdout," -v\t\tWrite a lot of progress messages\n");

fprintf(stdout," -n\t\tDon't remove large objects, just show what would be done\n");

fprintf(stdout," -U username\tUsername to connect as\n");

fprintf(stdout," -W\t\tPrompt forpassword\n");

fprintf(stdout," -W\t\tForcepassword prompt\n");

fprintf(stdout," -h hostname\tDatabase server host\n");

fprintf(stdout," -p port\tDatabase server port\n\n");

}

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/clusterdb.sgml,v 1.22 2007/06/04 10:02:40 petere Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/clusterdb.sgml,v 1.23 2007/12/11 19:57:32 tgl Exp $

PostgreSQL documentation

-->

<term><option>--password</></term>

<listitem>

<para>

Force password prompt.

Force <application>clusterdb</application> to prompt for a

password before connecting to a database.

</para>

<para>

This option is never essential, since

<application>clusterdb</application> will automatically prompt

for a password if the server demands password authentication.

However, <application>clusterdb</application> will waste a

connection attempt finding out that the server wants a password.

In some cases it is worth typing <option>-W</> to avoid the extra

connection attempt.

</para>

</listitem>

</varlistentry>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/createdb.sgml,v 1.46 2007/06/21 10:43:09 petere Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/createdb.sgml,v 1.47 2007/12/11 19:57:32 tgl Exp $

PostgreSQL documentation

-->

<term><option>--username <replaceable class="parameter">username</replaceable></></term>

<listitem>

<para>

User name to connect as

User name to connect as.

</para>

</listitem>

</varlistentry>

<term><option>--password</></term>

<listitem>

<para>

Force password prompt.

Force <application>createdb</application> to prompt for a

password before connecting to a database.

</para>

<para>

This option is never essential, since

<application>createdb</application> will automatically prompt

for a password if the server demands password authentication.

However, <application>createdb</application> will waste a

connection attempt finding out that the server wants a password.

In some cases it is worth typing <option>-W</> to avoid the extra

connection attempt.

</para>

</listitem>

</varlistentry>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/createlang.sgml,v 1.41 2007/05/15 19:43:51 neilc Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/createlang.sgml,v 1.42 2007/12/11 19:57:32 tgl Exp $

PostgreSQL documentation

-->

<term><option>--password</></term>

<listitem>

<para>

Force password prompt.

Force <application>createlang</application> to prompt for a

password before connecting to a database.

</para>

<para>

This option is never essential, since

<application>createlang</application> will automatically prompt

for a password if the server demands password authentication.

However, <application>createlang</application> will waste a

connection attempt finding out that the server wants a password.

In some cases it is worth typing <option>-W</> to avoid the extra

connection attempt.

</para>

</listitem>

</varlistentry>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/createuser.sgml,v 1.50 2007/06/21 12:20:10 petere Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/createuser.sgml,v 1.51 2007/12/11 19:57:32 tgl Exp $

PostgreSQL documentation

-->

<term><option>--password</></term>

<listitem>

<para>

Force password prompt (to connect to the server, not for the

Force <application>createuser</application> to prompt for a

password (for connecting to the server, not for the

password of the new user).

</para>

<para>

This option is never essential, since

<application>createuser</application> will automatically prompt

for a password if the server demands password authentication.

However, <application>createuser</application> will waste a

connection attempt finding out that the server wants a password.

In some cases it is worth typing <option>-W</> to avoid the extra

connection attempt.

</para>

</listitem>

</varlistentry>

</variablelist>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.33 2007/06/21 10:43:09 petere Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.34 2007/12/11 19:57:32 tgl Exp $

PostgreSQL documentation

-->

<term><option>--username <replaceable class="parameter">username</replaceable></></term>

<listitem>

<para>

User name to connect as

User name to connect as.

</para>

</listitem>

</varlistentry>

<term><option>--password</></term>

<listitem>

<para>

Force password prompt.

Force <application>dropdb</application> to prompt for a

password before connecting to a database.

</para>

<para>

This option is never essential, since

<application>dropdb</application> will automatically prompt

for a password if the server demands password authentication.

However, <application>dropdb</application> will waste a

connection attempt finding out that the server wants a password.

In some cases it is worth typing <option>-W</> to avoid the extra

connection attempt.

</para>

</listitem>

</varlistentry>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/droplang.sgml,v 1.30 2007/03/26 17:23:36 tgl Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/droplang.sgml,v 1.31 2007/12/11 19:57:32 tgl Exp $

PostgreSQL documentation

-->

<term><option>--username <replaceable class="parameter">username</replaceable></></term>

<listitem>

<para>

User name to connect as

User name to connect as.

</para>

</listitem>

</varlistentry>

<term><option>--password</></term>

<listitem>

<para>

Force password prompt.

Force <application>droplang</application> to prompt for a

password before connecting to a database.

</para>

<para>

This option is never essential, since

<application>droplang</application> will automatically prompt

for a password if the server demands password authentication.

However, <application>droplang</application> will waste a

connection attempt finding out that the server wants a password.

In some cases it is worth typing <option>-W</> to avoid the extra

connection attempt.

</para>

</listitem>

</varlistentry>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.38 2007/06/21 10:43:09 petere Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.39 2007/12/11 19:57:32 tgl Exp $

PostgreSQL documentation

-->

<term><option>--username <replaceable class="parameter">username</replaceable></></term>

<listitem>

<para>

User name to connect as (not the user name to drop)

User name to connect as (not the user name to drop).

</para>

</listitem>

</varlistentry>

<term><option>--password</></term>

<listitem>

<para>

Force password prompt (to connect to the server, not for the

password of the user to be dropped).

Force <application>dropuser</application> to prompt for a

password before connecting to a database.

</para>

<para>

This option is never essential, since

<application>dropuser</application> will automatically prompt

for a password if the server demands password authentication.

However, <application>dropuser</application> will waste a

connection attempt finding out that the server wants a password.

In some cases it is worth typing <option>-W</> to avoid the extra

connection attempt.

</para>

</listitem>

</varlistentry>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.97 2007/03/26 17:23:36 tgl Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.98 2007/12/11 19:57:32 tgl Exp $

PostgreSQL documentation

-->

<term><option>--username=<replaceable class="parameter">username</replaceable></option></term>

<listitem>

<para>

Connect as the given user.

User name to connect as.

</para>

</listitem>

</varlistentry>

<term><option>--password</option></term>

<listitem>

<para>

Force a password prompt. This should happen automatically if

the server requires password authentication.

Force <application>pg_dump</application> to prompt for a

password before connecting to a database.

</para>

<para>

This option is never essential, since

<application>pg_dump</application> will automatically prompt

for a password if the server demands password authentication.

However, <application>pg_dump</application> will waste a

connection attempt finding out that the server wants a password.

In some cases it is worth typing <option>-W</> to avoid the extra

connection attempt.

</para>

</listitem>

</varlistentry>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.68 2007/03/26 17:23:37 tgl Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.69 2007/12/11 19:57:32 tgl Exp $

PostgreSQL documentation

-->

<para>

<application>pg_dumpall</application> needs to connect several

times to the <productname>PostgreSQL</productname> server (once per

database). If you use password authentication itis likely to ask for

database). If you use password authentication itwill ask for

a password each time. It is convenient to have a

<filename>~/.pgpass</> file in such cases. See <xref

linkend="libpq-pgpass"> for more information.

<term>--username=<replaceable>username</replaceable></term>

<listitem>

<para>

Connect as the given user.

User name to connect as.

</para>

</listitem>

</varlistentry>

<term>--password</term>

<listitem>

<para>

Force a password prompt. This should happen automatically if

the server requires password authentication.

Force <application>pg_dumpall</application> to prompt for a

password before connecting to a database.

</para>

<para>

This option is never essential, since

<application>pg_dumpall</application> will automatically prompt

for a password if the server demands password authentication.

However, <application>pg_dumpall</application> will waste a

connection attempt finding out that the server wants a password.

In some cases it is worth typing <option>-W</> to avoid the extra

connection attempt.

</para>

<para>

Note that the password prompt will occur again for each database

to be dumped. Usually, it's better to set up a

<filename>~/.pgpass</> file than to rely on manual password entry.

</para>

</listitem>

</varlistentry>