<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.17 2000/04/11 14:43:54 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.18 2000/07/21 00:24:37 momjian Exp $
Postgres documentation
-->
To dump a database of the same name as the user:
<programlisting>
-% pg_dump > db.out
+$ pg_dump > db.out
</programlisting>
</para>
To reload this database:
<programlisting>
-% psql -e database < db.out
+$ psql -e database < db.out
</programlisting>
</para>
</refsect1>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.7 2000/01/24 19:34:13 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.8 2000/07/21 00:24:37 momjian Exp $
Postgres documentation
-->
To dump all databases:
<programlisting>
-% pg_dumpall > db.out
+$ pg_dumpall > db.out
</programlisting>
<tip>
To reload this database:
<programlisting>
-% psql -e template1 < db.out
+$ psql -e template1 < db.out
</programlisting>
</para>
<tip>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_passwd.sgml,v 1.2 2000/05/30 18:00:30 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_passwd.sgml,v 1.3 2000/07/21 00:24:37 momjian Exp $
Postgres documentation
-->
the new password for <literal>pg_guest</literal>:
<programlisting>
- % pg_passwd passwd
+ $ pg_passwd passwd
Username: pg_guest
Password:
Re-enter password:
The following lines show the sample usage of the option:
<programlisting>
-% psql -h hyalos -u unv
+$ psql -h hyalos -u unv
Username: pg_guest
Password:
Welcome to the POSTGRESQL interactive sql monitor:
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.9 2000/03/27 17:14:43 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.10 2000/07/21 00:24:37 momjian Exp $
Postgres documentation
-->
<para>
Then do:
<programlisting>
-% pg_dumpall -s >db.out
+$ pg_dumpall -s >db.out
</programlisting>
to dump out your old database's table definitions without any data.
</para>
<para>
Do
<programlisting>
-% make install
+$ make install
</programlisting>
to install the new binaries.
</para>
Change your working directory to the
pgsql main directory, and type:
<programlisting>
-% pg_upgrade -f db.out data.old
+$ pg_upgrade -f db.out data.old
</programlisting>
The program will do some checking to make sure everything is properly
configured, and will run your db.out script to recreate all the databases
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.9 2000/05/02 20:02:03 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.10 2000/07/21 00:24:37 momjian Exp $
Postgres documentation
-->
process already running on the same port number. The easiest way to
determine this is by using the command
<programlisting>
-% ps -ax | grep postmaster
+$ ps -ax | grep postmaster
</programlisting>
on BSD-based systems, or
<programlisting>
-% ps -e | grep postmast
+$ ps -e | grep postmast
</programlisting>
for System V-like or POSIX-compliant systems such as HP-UX.
</para>
should be used instead. Using
<programlisting>
-% kill -KILL
+$ kill -KILL
</programlisting>
or its alternative form
<programlisting>
-% kill -9
+$ kill -9
</programlisting>
will prevent <application>postmaster</application>
values, type:
<programlisting>
-% nohup postmaster >logfile 2>&1 &
+$ nohup postmaster >logfile 2>&1 &
</programlisting>
This command will start up <application>postmaster</application>
To start <application>postmaster</application> with a specific port:
<programlisting>
-% nohup postmaster -p 1234 &
+$ nohup postmaster -p 1234 &
</programlisting>
This command will start up <application>postmaster</application>
using psql, you would need to run it as
<programlisting>
-% psql -p 1234
+$ psql -p 1234
</programlisting>
or set the environment variable <envar>PGPORT</envar>:
<programlisting>
-% setenv PGPORT 1234
-% psql
+$ setenv PGPORT 1234
+$ psql
</programlisting>
</para>
</refsect1>