Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YQohN-0006Ts-Q7 for pgsql-hackers@arkaria.postgresql.org; Thu, 26 Feb 2015 03:01:13 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YQohN-0004Jg-4v for pgsql-hackers@arkaria.postgresql.org; Thu, 26 Feb 2015 03:01:13 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YQohL-0004Ja-Pc for pgsql-hackers@postgresql.org; Thu, 26 Feb 2015 03:01:11 +0000 Received: from mout.gmx.net ([212.227.17.21]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YQohI-0007VG-E1 for pgsql-hackers@postgresql.org; Thu, 26 Feb 2015 03:01:10 +0000 Received: from auth1-smtp.messagingengine.com ([66.111.4.227]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LlV4F-1Xq6dT2DMF-00bI0z for ; Thu, 26 Feb 2015 04:01:04 +0100 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailauth.nyi.internal (Postfix) with ESMTP id 687E020E2D for ; Wed, 25 Feb 2015 22:01:02 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Wed, 25 Feb 2015 22:01:03 -0500 X-Sasl-enc: yB7PVmiIzTWgsbzbSTs8ooJmu1d2DLyAes5NvQ1mDUQ1 1424919663 Received: from [10.0.0.36] (unknown [67.165.24.246]) by mail.messagingengine.com (Postfix) with ESMTPA id D28A66800C6; Wed, 25 Feb 2015 22:01:02 -0500 (EST) Message-ID: <54EE8C6E.8090506@gmx.net> Date: Wed, 25 Feb 2015 22:01:02 -0500 From: Peter Eisentraut User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Stephen Frost CC: Adam Brightwell , Noah Misch , Tom Lane , PostgreSQL Hackers Subject: Re: CATUPDATE confusion? References: <20141227080926.GA2035611@tornado.leadboat.com> <20141227151034.GU3062@tamriel.snowman.net> <28382.1419703324@sss.pgh.pa.us> <20141227231829.GX3062@tamriel.snowman.net> <1952.1419722762@sss.pgh.pa.us> <20141227233150.GA2046947@tornado.leadboat.com> <54E65000.8030304@gmx.net> <20150225203955.GY29780@tamriel.snowman.net> In-Reply-To: <20150225203955.GY29780@tamriel.snowman.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:IRxKkczvKHmp+OE/RawCA6ffs6sbEMwHJF86Z7oEdLj7f7sOztl sIltm6SoeDQv7eIDX9cy64JOEISse+49XMSgIQoo94BCyTedekYvMdzbMoL/l9ldhAdEme7 PTektfFCaCpJun5Qs/rpEUt3CMMx8rFZQ6B8MdKihT16CsimfNYh69tGu8SPKhcQV+/9/Va Gf/PzPzQh0PSdqtcfbngw== X-UI-Out-Filterresults: notjunk:1; X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 2/25/15 3:39 PM, Stephen Frost wrote: >> I'd get rid of that whole check, not just replace rolcatupdate by rolsuper. > > Err, wouldn't this make it possible to grant normal users the ability to > modify system catalogs? I realize that they wouldn't have that > initially, but I'm not sure we want the superuser to be able to grant > that to non-superusers.. Why not? I thought we are trying to get rid of special superuser behavior. After all, superusers can also make the other user a superuser to bypass this issue. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers