From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, John McKown <joarmc(at)swbell(dot)net>, Postgresql Docs ML <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: the docs, and newbies. |
Date: | 2001-01-22 16:59:41 |
Message-ID: | 21890.980182781@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
"Ross J. Reedstrom" <reedstrm(at)rice(dot)edu> writes:
> 'Admin' is shorter, has just as long a precedent (or longer) than
> superuser, has more of the _right_ connotations in the database community,
> and none of the overloading concerning system priviliges that 'superuser'
> has.
"Admin" might work. Thinking about this some more, I realize that there
are three distinct concepts that we are fuzzing together. It might help
if we adopted different terms for:
* The actual *person* responsible for the database. Use in contexts
like "The DBA must make sure that ...". In some places we avoid this
by using the pronoun "you", but people often find that too informal.
* The Unix account ID under which the postmaster runs. The existing
docs mostly refer to this as "the postgres account", which is a problem
because one keeps wanting to add an asterisk to it ("* or whatever
account you are running the postmaster under").
* The one or more Postgres usernames that are marked "usesuper" in
pg_shadow. If we keep the term "superuser" it should be reserved
for this meaning.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-01-22 17:16:56 | Re: MS FAQ |
Previous Message | Ross J. Reedstrom | 2001-01-22 16:46:17 | Re: the docs, and newbies. |