Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAC6IPs22710 for ; Sun, 12 Nov 2000 01:18:25 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eAC6HPD22801; Sun, 12 Nov 2000 01:17:25 -0500 (EST) To: Peter Eisentraut cc: pgsql-docs@postgresql.org Subject: Re: System application reference pages In-reply-to: <3A0E1FC5.A8D172AE@wgcr.org> References: <3A0E1FC5.A8D172AE@wgcr.org> Comments: In-reply-to Lamar Owen message dated "Sat, 11 Nov 2000 23:42:45 -0500" Date: Sun, 12 Nov 2000 01:17:25 -0500 Message-ID: <22798.974009845@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200011/33 X-Sequence-Number: 36 >>>> The manual pages for initdb, initlocation, ipcclean, pg_passwd, >>>> pg_upgrade, postgres, and postmaster should be moved to the >>>> Administrator's Guide, because their usage is subject of the Admin Guide >>>> and not of the User's Guide. Comments? Surely pg_ctl also belongs in that group. One could make an argument that pg_dump, pg_dumpall, pg_restore, and vacuumdb do too, though it'd be a weaker argument. Also createuser, dropuser, perhaps createlang/droplang. All of these require superuser privs to be more than marginally useful, so they strike me as primarily admin tools not user tools. regards, tom lane