From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] users in Postgresql |
Date: | 1999-11-07 16:44:10 |
Message-ID: | Pine.LNX.4.20.9911071733490.7643-100000@peter-e.yi.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 1999-11-02, Bruce Momjian mentioned:
> CREATE USER sql command updates the file, but an UPDATE on pg_shadow
> does not.
How about INSERT INTO pg_shadow? Or how do you judge the following excerpt
from the createuser script:
QUERY="insert into pg_shadow \
(usename, usesysid, usecreatedb, usetrace, usesuper, usecatupd) \
values \
('$NEWUSER', $SYSID, '$CANCREATE', 'f', '$CANADDUSER','f')"
Fortunately (perhaps), I am getting rid of this as we're speaking. The one
feature the createuser script has over the CREATE USER "SQL" command is
that you can pick your system ID. Ignoring the question whether or not
this has any real purpose, it seems this is almost like rolling dice since
you cannot ever reliably change that later. (And I'm not even talking
about the fact that the sysid is a primary key and there is no referential
integrity enforced.)
So is anyone strictly opposed to yanking that feature? And perhaps
removing all references to user sysids in the (user) documentation?
-Peter
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Stuart Woolford | 1999-11-07 23:50:41 | more] indexed regex select optimisations? |
Previous Message | Gavin Clark | 1999-11-07 10:33:31 | Re: Installing Postgresql |
From | Date | Subject | |
---|---|---|---|
Next Message | Keith Parks | 1999-11-07 16:51:57 | New psql input mode problems |
Previous Message | Bruce Momjian | 1999-11-07 14:16:54 | What is nameout() for? |