From: | "Nauman Naeem" <nauman(dot)naeem(at)gmail(dot)com> |
---|---|
To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: User privileges-verification required |
Date: | 2006-02-27 16:09:50 |
Message-ID: | 211765b50602270809v7f626ce9i4ea2f1e3a9362162@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 minimum functionality should be a part of
multiuser mode! I was oblivious of this and did initdb twice, may be I am
dumb :-)
Thanks,
Nauman
On 2/26/06, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> wrote:
>
> > 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 "NOCREATEUSER" command.
>
> I agree :)
>
> Chris
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2006-02-27 16:21:08 | Any conclusion on the Xeon context-switching issue? |
Previous Message | Martijn van Oosterhout | 2006-02-27 16:03:17 | Re: pg_config, pg_service.conf, postgresql.conf .... |