Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id A82891338630 for ; Thu, 14 Oct 2010 06:07:56 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 00391-01-8 for ; Thu, 14 Oct 2010 09:07:48 +0000 (UTC) Received: from mx3.hub.org (mx3.hub.org [206.223.169.73]) by mail.postgresql.org (Postfix) with ESMTP id D8B9D133807C for ; Wed, 13 Oct 2010 18:40:23 -0300 (ADT) X-Greylist: delayed 00:11:40.177896 by SQLgrey-1.7.6 Received: from sd-17937.dedibox.fr (sd-17937.dedibox.fr [88.191.100.74]) by mx3.hub.org (Postfix) with ESMTP id 394EC37B53D for ; Wed, 13 Oct 2010 18:40:24 -0300 (ADT) Received: from [192.168.0.6] (uni14-1-82-233-223-216.fbx.proxad.net [82.233.223.216]) by sd-17937.dedibox.fr (Postfix) with ESMTPA id 272B73B8F5; Wed, 13 Oct 2010 23:20:03 +0200 (CEST) Message-ID: <4CB62282.1070408@lelarge.info> Date: Wed, 13 Oct 2010 23:20:02 +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> In-Reply-To: <232B5217AD58584C87019E8933556D1102199CC548@redmx2.esri.com> 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, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/115 X-Sequence-Number: 35856 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. Thanks for your inputs. -- Guillaume http://www.postgresql.fr http://dalibo.com