Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 7D22A1337C18 for ; Fri, 15 Oct 2010 19:25:03 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 48345-06 for ; Fri, 15 Oct 2010 22:24:56 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sd-17937.dedibox.fr (sd-17937.dedibox.fr [88.191.100.74]) by mail.postgresql.org (Postfix) with ESMTP id 98F591337BF9 for ; Fri, 15 Oct 2010 19:24:54 -0300 (ADT) Received: from [192.168.1.7] (164.92.92-79.rev.gaoland.net [79.92.92.164]) by sd-17937.dedibox.fr (Postfix) with ESMTPA id A3E433B8F5; Sat, 16 Oct 2010 00:24:54 +0200 (CEST) Message-ID: <4CB8D4B6.2000500@lelarge.info> Date: Sat, 16 Oct 2010 00:24:54 +0200 From: Guillaume Lelarge User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); fr; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Kasia Tuszynska CC: pgsql-admin Subject: Re: two questions about pg 9.0 References: <1508171717.69491.1286831195955.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> <7815.1286839244@sss.pgh.pa.us> <232B5217AD58584C87019E8933556D1102198CA98C@redmx2.esri.com> <4CB4A1F9.60408@lelarge.info> <232B5217AD58584C87019E8933556D1102199CC548@redmx2.esri.com> <4CB62282.1070408@lelarge.info> In-Reply-To: <4CB62282.1070408@lelarge.info> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201010/137 X-Sequence-Number: 35878 Le 13/10/2010 23:20, Guillaume Lelarge a écrit : > Hi Kasia, > > Le 13/10/2010 22:21, Kasia Tuszynska a écrit : >> [...] >> Thanks for your reply I did a bit more testing with the superuser priv issue, and now I came to the conclusion that pgAdminIII may be doing something silly. >> > > Sure, that happens more than I would like. > >> I created a user: bob >> >> 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... >> > > I would not call it a feature. I find this misleading too. I'm too tired > right now to work on a fix, but it'll be easy and quick to do. > > I have a few things to commit tomorrow. I'll try to work on this at the > same time. > I commited a fix. It should be available when 1.12.2 will be released. -- Guillaume http://www.postgresql.fr http://dalibo.com