From: | Matthew <matt(at)ctlno(dot)com> |
---|---|
To: | "'Trewern, Ben'" <Ben(dot)Trewern(at)mowlem(dot)com>, "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | RE: Drop a user leaves permissions! |
Date: | 2001-02-13 20:43:38 |
Message-ID: | 183FA749499ED311B6550000F87E206C1FCFE4@srv.ctlno.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have seen this before myself, and I agree it is less then optimal. I
would think that it's a place where referential integrity should be used.
Either don't allow you to drop the user until all permissions are removed,
or automatically remove all permissions, cascade delete type of thing.
> -----Original Message-----
> From: Trewern, Ben [SMTP:Ben(dot)Trewern(at)mowlem(dot)com]
> Sent: Tuesday, February 13, 2001 11:10 AM
> To: 'pgsql-general(at)postgresql(dot)org'
> Subject: [GENERAL] Drop a user leaves permissions!
>
> I'm using PostgreSQL and I've been working with permissions.
> I've tried the following:
>
> CREATE USER ben;
> GRANT ALL ON table1 TO ben;
> DROP USER ben;
>
> The permissions get left to the table as in :
>
> Relation | Access permissions
> ------------------------------------------------------
> table1 | {"=","51=arwR"}
>
> I assume that 51 is the ID of the user who was dropped.
> Is this a bug? How should I clean up the permissions?
>
> thanks
>
> Ben
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew | 2001-02-13 20:55:26 | RE: O'Reilly Conference Proposals |
Previous Message | Bruce Momjian | 2001-02-13 20:36:40 | O'Reilly Conference Proposals |