From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | [pgAdmin III] #257: UI glitch with superuser /canupdatecatalogs |
Date: | 2010-10-15 22:21:24 |
Message-ID: | 056.f40facc27ea8e639d7fb0fde8de5d76a@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#257: UI glitch with superuser /canupdatecatalogs
-----------------------------+----------------------------------------------
Reporter: Kasia Tuszynska | Owner: gleu
Type: bug | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: 1.12
Keywords: role | Platform: all
-----------------------------+----------------------------------------------
In pgAdminIII I checked off the box for: can inherit from parent role, can
create db object, superuser
Got the following sql:
CREATE ROLE bob LOGIN
ENCRYPTED PASSWORD 'md51e9484aace238e7cb2609130fd87646e'
SUPERUSER INHERIT CREATEDB NOCREATEROLE;
UPDATE pg_authid SET rolcapupdate=false WHERE rolname='bob';
Than I created bobb
In pgAdminIII I checked off the box for: can inherit from parent role, can
create db object, superuser, Can modify catalog directly
Got the following sql:
CREATE ROLE bobb LOGIN
ENCRYPTED PASSWORD 'md51e9484aace238e7cb2609130fd87646e'
SUPERUSER INHERIT CREATEDB NOCREATEROLE;
Conclusion:
Sql level superuser = pgAdminIII superuser + can modify catalog directly
This is misleading, I would call it a pgAdminIII bug but who knows maybe
it is a feature...
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/257>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2010-10-15 22:22:21 | pgAdmin III commit: Fix the setting of "Can update catalog" checkbox |
Previous Message | pgAdmin Trac | 2010-10-14 16:30:09 | [pgAdmin III] #256: Add triggers on views support |