pgintro now has a list of all manual pages.

diff --git a/src/man/pgintro.1 b/src/man/pgintro.1
index 8801b6ed226d9b97b536d7cb92a1e8fea5523591..c2b145aa710136edfaed8604162a92227600cd9e 100644 (file)
--- a/src/man/pgintro.1
+++ b/src/man/pgintro.1
@@ -1,6 +1,6 @@
 .\" This is -*-nroff-*-
 .\" XXX standard disclaimer belongs here....
-.\" $Header: /cvsroot/pgsql/src/man/Attic/pgintro.1,v 1.3 1998/01/26 01:42:50 scrappy Exp $
+.\" $Header: /cvsroot/pgsql/src/man/Attic/pgintro.1,v 1.4 1998/04/15 16:44:36 momjian Exp $
 .TH PGINTRO UNIX 11/05/95 PostgreSQL PostgreSQL
 .SP INFORMATION UNIX 11/05/95
 .BH "SECTION 2 - Unix COMMANDS (Unix)"
@@ -161,21 +161,35 @@ access controls.  This is an inherent problem with user-defined C functions.
 Like SQL functions, rules always run with the identity and
 permissions of the user who invoked the backend server.
 .SH "SEE ALSO"
-postmaster(1),
-alter(l),
-insert(l),
-grant/revoke(l),
-copy(l),
-create(l),
-delete(l),
-drop table(l),
-drop index(l),
-drop rule(l),
-update(l),
-select(l),
-kerberos(1),
-kinit(1),
-kerberos(3)
+.nf
+abort(l)                declare(l)              large_objects(3)
+alter_table(l)          delete(l)               libpq(3)
+alter_user(l)           destroydb(1)            listen(l)
+begin(l)                destroyuser(1)          load(l)
+bki(5)                  drop(l)                 lock(l)
+catalogs(3)             drop_aggregate(l)       move(l)
+cleardbdir(1)           drop_database(l)        notify(l)
+close(l)                drop_function(l)        oracle_compat(3)
+cluster(l)              drop_index(l)           page(5)
+commit(l)               drop_language(l)        pg_dump(1)
+copy(l)                 drop_operator(l)        pg_dumpall(1)
+create_aggregate(l)     drop_rule(l)            pg_hba(conf(5)
+create_database(l)      drop_sequence(l)        pg_passwd(1)
+create_function(l)      drop_table(l)           pgbuiltin(3)
+create_index(l)         drop_trigger(l)         pgintro(1)
+create_language(l)      drop_type(l)            postgres(1)
+create_operator(l)      drop_user(l)            postmaster(1)
+create_rule(l)          drop_view(l)            psql(1)
+create_sequence(l)      ecpg(1)                 reset(l)
+create_table(l)         end(l)                  revoke(l)
+create_trigger(l)       explain(l)              rollback(l)
+create_type(l)          fetch(l)                select(l)
+create_user(l)          grant(l)                set(l)
+create_version(l)       initdb(1)               show(l)
+create_view(l)          initlocation(1)         sql(l)
+createdb(1)             insert(l)               update(l)
+createuser(1)           ipcclean(1)             vacuum(l)
+.fi
 .SH CAVEATS 
 .PP
 There are no plans to explicitly support encrypted data inside of