Thread: pgsql: Update for roles: < * Allow limits on per-db/user connections >

Log Message:
-----------
Update for roles:

< * Allow limits on per-db/user connections
> * Allow limits on per-db/role connections
< * Prevent default re-use of sysids for dropped users and roles
<
<   Currently, if a user is removed while he still owns objects, a new
<   user given might be given their user id and inherit the
<   previous users objects.
<
450c444
< * Add COMMENT ON for all cluster global objects (users, roles, databases
> * Add COMMENT ON for all cluster global objects (roles, databases
609c603
<       users and roles with separate DROP commands
>       roles with separate DROP commands

Modified Files:
--------------
    pgsql/doc:
        TODO (r1.1584 -> r1.1585)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1584&r2=1.1585)
    pgsql/doc/src/FAQ:
        TODO.html (r1.91 -> r1.92)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.91&r2=1.92)

momjian@svr1.postgresql.org (Bruce Momjian) writes:
> < * Prevent default re-use of sysids for dropped users and roles
> <
> <   Currently, if a user is removed while he still owns objects, a new
> <   user given might be given their user id and inherit the
> <   previous users objects.
> <

It's a bit premature to declare victory on that front.  If Alvaro
doesn't finish the shared-dependencies patch in time, we are going
to have to continue the old kluge of letting people assign a sysid
(which would now be interpreted as assigning an OID).  Otherwise
there's no way to recover fully from dropping a user who still owns
objects.

            regards, tom lane