Yeah it really was :-) BTW I have implemented this for multiuser-mode as well..Both the approaches as mentioned in my very first email...
1- The minimum super user count should not be less then 1.
2- Only the main database system owner is eligible to reassign.
My personal believe is, this m
In my opinion we should cater for such a situation, and two possible
solutions come to my mind for this:
I've done exactly this before, and had to use single user mode to
recover. Annoying.
1. Place a restriction that there should be more than one superuser
before you can issue a "NOCREATEU
"Nauman Naeem" <[EMAIL PROTECTED]> writes:
> I tried the single-user mode option and it worked, thanks! but, don't
> you people think that we should provide this privilege in multi-user
> mode as well.In accordence to my second point.
No. Restricting what a superuser can do is pointless --- he ca
I tried the single-user mode option and it worked, thanks! but, don't
you people think that we should provide this privilege in multi-user
mode as well.In accordence to my second point.
On 2/24/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Am Freitag, 24. Februar 2006 14:25 schrieb Nauman Naee
Am Freitag, 24. Februar 2006 14:25 schrieb Nauman Naeem:
> In case I have only one user in my database who is also the DBSystem
> (who carries out initdb), user then if that user takes away his
> "createuser" privileges, he is unable to grant himself that privilege
> again or grant that privilege t
Hello all,
While playing around with database users, I noticed one odd thing
regarding user privileges.
In case I have only one user in my database who is also the DBSystem
(who carries out initdb), user then if that user takes away his
"createuser" privileges, he is unable to grant himself that
