From: | Erwin Brandstetter <brandstetter(at)falter(dot)at> |
---|---|
To: | dpage(at)postgresql(dot)org |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: SQL for CREATE ROLE xxx SUPERUSER |
Date: | 2007-08-16 15:36:15 |
Message-ID: | 46C46EEF.3060406@falter.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
dpage(at)postgresql(dot)org wrote:
> Erwin Brandstetter wrote:
>> Second example: superusers get an extra line "UPDATE ..." that should
>> not be there. Especially as it refers to the OID which would be
>> different when recreating the user.
>> CREATE ROLE tester2 SUPERUSER;
>>
>> === quote
>> -- Role: "tester2"
>>
>> -- DROP ROLE tester2;
>>
>> CREATE ROLE tester2
>> SUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
>> UPDATE pg_authid SET rolcatupdate=true WHERE OID=3714960::oid;
>> === unquote
>
> Hi Erwin,
>
> The update is supposed to be there - it enables direct catalog updates
> for the user - a kind of super-superuser. You're correct about using
> the OID though - replaced with the rolname.
Hi Dave!
But is the line needed at all?
Clearly it works the same way with just "CREATE ROLE tester SUPERUSER".
LG
Erwin
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2007-08-16 15:46:20 | Re: SQL for CREATE ROLE xxx SUPERUSER |
Previous Message | Dave Page | 2007-08-16 14:58:59 | Re: SQL for CREATE ROLE xxx SUPERUSER |