Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j0BgJ-0006xC-9F for pgsql-bugs@arkaria.postgresql.org; Fri, 07 Feb 2020 22:00:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j0BgG-0003nj-Di for pgsql-bugs@arkaria.postgresql.org; Fri, 07 Feb 2020 22:00:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j0BgG-0003nc-5b for pgsql-bugs@lists.postgresql.org; Fri, 07 Feb 2020 22:00:56 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j0BgD-0007Jo-AS for pgsql-bugs@lists.postgresql.org; Fri, 07 Feb 2020 22:00:55 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 017M0pV1023537; Fri, 7 Feb 2020 17:00:51 -0500 From: Tom Lane To: randolph.a.strauss@nasa.gov cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16250: As the owner of a database, I can't CREATE EXTENSION postgis; In-reply-to: <16250-5dda0be64da14e53@postgresql.org> References: <16250-5dda0be64da14e53@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Fri, 07 Feb 2020 21:36:50 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <23535.1581112851.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 07 Feb 2020 17:00:51 -0500 Message-ID: <23536.1581112851@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > There's no point being able to create a database if one can't add the > extensions one needs. > We need postgis, postgis_topology, uuid-ossp, hstore > How about adding a privilege to control this, instead of forcing the > superuser password to be given out? This is being worked on [1][2]. regards, tom lane [1] https://www.postgresql.org/message-id/flat/5889.1566415762%40sss.pgh.p= a.us [2] https://www.postgresql.org/message-id/flat/32315.1580326876%40sss.pgh.= pa.us