From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | schmidtm <schmidtm(at)mock-software(dot)de> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: somebody working on: Prevent default re-use of sysids for dropped users and groups? |
Date: | 2004-12-03 22:58:55 |
Message-ID: | 15505.1102114735@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
schmidtm <schmidtm(at)mock-software(dot)de> writes:
> is somebody working on these two issues on the TODO-List?
> 1) Prevent default re-use of sysids for dropped users and groups
I don't know of anyone actively working on it, but if you check the
archives you'll find that the preferred solution approach is pretty well
hashed out --- it boils down to creating a shared sequence object and
using that, rather than a MAX(sysid) query, to select default sysids.
The painful part of this is just that bootstrap mode doesn't currently
have any support for creating sequences. I don't think fixing that will
be hugely hard, but it might be a bit tedious.
> 2) Prevent dropping user that still owns objects, or auto-drop the
> objects
No one has any idea how to do this reasonably --- the problem is you
have no visibility into databases other than the one you're connected
to, so you can't tell what the user owns in other databases.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2004-12-03 23:12:20 | Re: somebody working on: Prevent default re-use of sysids |
Previous Message | Andrew Dunstan | 2004-12-03 22:41:28 | Re: OK, ready for RC1 or Beta6 |