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:[EMAIL PROTECTED]]
> Sent: Tuesday, February 13, 2001 11:10 AM
> To: '[EMAIL PROTECTED]'
> 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
