Re: somebody working on: Prevent default re-use of sysids for dropped users and groups? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: somebody working on: Prevent default re-use of sysids for dropped users and groups?
Date
Msg-id 20041211163107.GA20836@dcc.uchile.cl
Whole thread Raw
In response to Re: somebody working on: Prevent default re-use of sysids for dropped users and groups?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: somebody working on: Prevent default re-use of sysids for dropped users and groups?
Re: somebody working on: Prevent default re-use of sysids for dropped users and groups?
List pgsql-hackers
On Mon, Dec 06, 2004 at 05:27:32PM -0500, Tom Lane wrote:

Hi,

> So if Alvaro's thing works out, the shared-sequence problem becomes moot.
> Probably that's a good reason not to spend time on it just yet.

I'm still alive, and I've been following this thread.  Sorry for not
giving an update.

I have been working on the patch and it seems now it works as I
originally intended it to: dropping users or tablespaces is disallowed
unless they own or contain no object.  ACL's are not tracked; I'm still
unsure if they should be.  It should not be a difficult modification
though.

Now, with the current setup there are 3000-and-some entries per
database.  This makes it by a wide margin the biggest shared catalog.
Is this something to be concerned with?  Adding ACL tracking won't make
it any more bloated on a freshly initdb'd database, but it will grow
much faster.

I had thought that maybe we shouldn't track dependencies on the first
superuser, on the assumption that it cannot be dropped.  I'm not sure if
this is entirely true however.


I'll post the patch on monday or tuesday for review and testing.

-- 
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"Puedes vivir solo una vez, pero si lo haces bien, una vez es suficiente"


pgsql-hackers by date:

Previous
From: mweilguni@sime.com
Date:
Subject: Minor Optimization?
Next
From: Tom Lane
Date:
Subject: Re: old-style handler problem