From: | Daniel Kalchev <daniel(at)digsys(dot)bg> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: DROP USER weirdness in 7.2.1 |
Date: | 2002-10-16 07:48:02 |
Message-ID: | 200210160748.g9G7m2u03095@dcave.digsys.bg |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>Peter Eisentraut said:
> Daniel Kalchev writes:
>
> > One would normally expect, that when DROP USER someuser is issued, all
> > associated data structures will be readjusted, especially ownership and ac
cess
> > rights.
>
> Perhaps, but the documentation states otherwise.
>
[...]
> > Any resolution for this?
>
> Recreate the user with the given ID and drop the objects manually.
I was able to modify ownership of all tables using ALTER TABLE. However, the
associated pg_toastXXXX tables still remain with the wrong ownership.
In my case, I had to recreate the user, because it had to have rights in a
different database within the same postgres installation... Nevertheless, it
would be much more convenient, if ALL rights associated with the particular
users are dropped when the user is dropped and eventually all orphaned objects
have their owner set to the DBA (postgres).
It is not too difficult to imagine, that in real-world database installation
users would need to be created and dropped.
Daniel
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Clift | 2002-10-16 08:34:52 | Re: Postgresql and multithreading |
Previous Message | Gavin Sherry | 2002-10-16 07:29:37 | Re: Vacuum improvement |