Re: pgsql: Update for roles: < * Allow limits on per-db/user connections > - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Update for roles: < * Allow limits on per-db/user connections >
Date
Msg-id 20806.1120246857@sss.pgh.pa.us
Whole thread Raw
In response to pgsql: Update for roles: < * Allow limits on per-db/user connections >  (momjian@svr1.postgresql.org (Bruce Momjian))
List pgsql-committers
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

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Update for roles: < * Prevent default re-use
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Avoid function name conflict when plpgsql and rangefuncs