pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
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;
Date: Fri, 07 Feb 2020 17:00:51 -0500
Message-ID: <23536.1581112851@sss.pgh.pa.us> (raw)
In-Reply-To: <16250-5dda0be64da14e53@postgresql.org>
References: <16250-5dda0be64da14e53@postgresql.org>

PG Bug reporting form <noreply@postgresql.org> 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.pa.us
[2] https://www.postgresql.org/message-id/flat/32315.1580326876%40sss.pgh.pa.us





view thread (2+ messages)

Message-ID: <23536.1581112851@sss.pgh.pa.us>
Permalink:  ../23536.1581112851@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/23536.1581112851@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, randolph.a.strauss@nasa.gov
  Subject: Re: BUG #16250: As the owner of a database, I can't CREATE EXTENSION postgis;
  In-Reply-To: <23536.1581112851@sss.pgh.pa.us>
  References: <16250-5dda0be64da14e53@postgresql.org> <23536.1581112851@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox