From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: dropping a user causes pain (#2) |
Date: | 2003-08-11 02:49:43 |
Message-ID: | 3F370447.5080603@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The docs (new and old) explicitly state you can do this; see for example
http://www.postgresql.org/docs/7.3/static/sql-dropuser.html
But ISTM that in such a case the user's objects should possibly be
reassigned to the database owner (who can't be dropped), in kinda the
same way that a *nix process that is orphaned is reparented to init. I
guess that might break other things, or would it?
Or maybe we need 'drop user foo with cascade'.
Or both.
cheers
andrew
Christopher Kings-Lynne wrote:
>Hi,
>
>I dropped the owner of a table (with no complaints), and now I get this:
>
>psql:
>
>asdf=# \dt
> List of relations
> Schema | Name | Type | Owner
>--------+------+-------+------------
> public | a1 | table |
>
>pg_dump:
>
>pg_dump: WARNING: owner of data type "a1" appears to be invalid
>pg_dump: WARNING: owner of table "a1" appears to be invalid
>
>Didn't there used to be a check that occurred, preventing you from dropping
>a user who owned objects?
>
>Chris
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 7: don't forget to increase your free space map settings
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-08-11 03:01:42 | Re: dropping a user causes pain (#2) |
Previous Message | Christopher Kings-Lynne | 2003-08-11 02:13:18 | dropping a user causes pain (#2) |