Re: Command names

From: "Adam Lang" <aalang(at)rutgersinsurance(dot)com>
To: "PGSQL General" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Command names
Date: 2000-09-28 14:37:46
Message-ID: 007201c02959$ab662480$330a0a0a@Adam
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'd assume a problem with changing all the commands now is that it may break
a lot of people's scripts and programs.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Keith L. Musser" <kmusser(at)idisys(dot)com>
To: "PGSQL-General" <pgsql-general(at)postgresql(dot)org>
Sent: Thursday, September 28, 2000 9:39 AM
Subject: [GENERAL] Command names

I know all of you are accustomed to the command line interface for pgsql.
(Of course, some of you created it!) However, I'd be interested if anyone
else feels the way I do....

I would prefer to have a consistent set of names for the commands. For
example,
I propose the following:

Instead of this use this.
----------------------------------------------------
createdb pg_createdb
createuser pg_createuser
destroydb pg_destroydb
initdb pg_initdb
initlocation pg_initlocation
pgaccess pg_accessgui
pgadmin pg_admin
pg_dump pg_dump
pg_dumpall pg_dumpall
postgres pg_single
postmaster pg_master
psql pg_access
vacuumdb pg_vacuumdb
??? pg_help (list all these commands)

Not that it is terribly difficult the way it is. But I simply think that a
consistent set of names would help new users, and help to prevent conflicts
with other commands in the PATH. Any comments?

- Keith

Keith L. Musser
Integrated Dynamics, Inc.
812-371-7777
email: kmusser(at)idisys(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2000-09-28 14:54:02 Re: Command names
Previous Message Efrain Caro 2000-09-28 14:28:37 Re: Command names