pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #16250: As the owner of a database, I can't CREATE EXTENSION postgis;
2+ messages / 2 participants
[nested] [flat]
* BUG #16250: As the owner of a database, I can't CREATE EXTENSION postgis;
@ 2020-02-07 21:36 PG Bug reporting form <noreply@postgresql.org>
2020-02-07 22:00 ` Re: BUG #16250: As the owner of a database, I can't CREATE EXTENSION postgis; Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2020-02-07 21:36 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: randolph.a.strauss@nasa.gov
The following bug has been logged on the website:
Bug reference: 16250
Logged by: Randy Strauss
Email address: randolph.a.strauss@nasa.gov
PostgreSQL version: 10.5
Operating system: Mac
Description:
The documentation looks identical for 10.5 and 12 with respect to
extensions.
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?
I don't know if this is a bug. I don't see it on the FAQ or TODO list...
I don't see a "requires superuser" field in the pg_extension table...
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #16250: As the owner of a database, I can't CREATE EXTENSION postgis;
2020-02-07 21:36 BUG #16250: As the owner of a database, I can't CREATE EXTENSION postgis; PG Bug reporting form <noreply@postgresql.org>
@ 2020-02-07 22:00 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2020-02-07 22:00 UTC (permalink / raw)
To: randolph.a.strauss@nasa.gov; +Cc: pgsql-bugs@lists.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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2020-02-07 22:00 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-02-07 21:36 BUG #16250: As the owner of a database, I can't CREATE EXTENSION postgis; PG Bug reporting form <noreply@postgresql.org>
2020-02-07 22:00 ` Tom Lane <tgl@sss.pgh.pa.us>
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