From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Stephen Martin" <stephen(at)sealteam(dot)demon(dot)co(dot)uk> |
Cc: | pgsql-interfaces(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] Date: Sat, 26 Feb 2000 17:01:55 -0800 |
Date: | 2000-02-27 01:47:08 |
Message-ID: | 22648.951616028@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
"Stephen Martin" <stephen(at)sealteam(dot)demon(dot)co(dot)uk> writes:
> For example I have a postgres id 'www' present within my pg_shadow/pg_user.
> I recently installed a package and inadvertantly created another 'www' user.
> How can I
> 1) Ensure I canot in future create duplicate names?
There should probably be a unique index on pg_shadow's usename field,
and another one on the usesysid field (otherwise there's not a unique
map from sysids to users, which is bad since we use sysids as
referential keys in other tables).
I'm surprised this hasn't been pointed out before :-(
I'm not sure how difficult it would be to do it. Just creating
an index with CREATE INDEX will not work, because pg_shadow is
an installation-wide table and its index must be as well. There's
some routine somewhere in the backend that would have to be taught
about the index.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-02-27 04:48:49 | update_pg_pwd trigger does not work very well |
Previous Message | Stephen Martin | 2000-02-27 01:15:34 | RE: [INTERFACES] Date: Sat, 26 Feb 2000 17:01:55 -0800 |
From | Date | Subject | |
---|---|---|---|
Next Message | Willy De la Court | 2000-02-27 14:16:37 | pgsql ODBC driver and Visual Foxpro |
Previous Message | Stephen Martin | 2000-02-27 01:15:34 | RE: [INTERFACES] Date: Sat, 26 Feb 2000 17:01:55 -0800 |