#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
--
Sent via pgadmin-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
