pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedcreate function - user permissions
3+ messages / 3 participants
[nested] [flat]
* create function - user permissions
@ 2000-07-21 23:44 Markus Wagner <mawagner@mail.uni-mainz.de>
0 siblings, 2 replies; 3+ messages in thread
From: Markus Wagner @ 2000-07-21 23:44 UTC (permalink / raw)
To: pgsql-sql
Hi,
one of my users wants to create functions using the C language, but pgs
says "no permission".
How can I permit the user to do this, while avoiding to give him root
access rights?
Thanks,
Markus
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: create function - user permissions
@ 2000-07-22 06:03 Tom Lane <tgl@sss.pgh.pa.us>
parent: Markus Wagner <mawagner@mail.uni-mainz.de>
1 sibling, 0 replies; 3+ messages in thread
From: Tom Lane @ 2000-07-22 06:03 UTC (permalink / raw)
To: markus.wagner@bigfoot.com; +Cc: pgsql-sql
Markus Wagner <mawagner@mail.uni-mainz.de> writes:
> one of my users wants to create functions using the C language, but pgs
> says "no permission".
> How can I permit the user to do this, while avoiding to give him root
> access rights?
Just a wakeup call here: if you let a user write C functions then
you *are* giving him Postgres superuser rights. He can do anything
he damn well pleases as user postgres, he's just got to write some
code to do it.
Once you've absorbed that, giving him the dbadmin password should
not look unreasonable.
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: create function - user permissions
@ 2000-07-22 09:11 Jan Wieck <JanWieck@t-online.de>
parent: Markus Wagner <mawagner@mail.uni-mainz.de>
1 sibling, 0 replies; 3+ messages in thread
From: JanWieck@t-online.de @ 2000-07-22 09:11 UTC (permalink / raw)
To: markus.wagner@bigfoot.com; +Cc: pgsql-sql
Markus Wagner wrote:
> Hi,
>
> one of my users wants to create functions using the C language, but pgs
> says "no permission".
>
> How can I permit the user to do this, while avoiding to give him root
> access rights?
Assuming with "root" access you mean "DB-superuser" rights.
No way!
From the C language, he has total access to the DB backend,
running under the OS-side database system owners UID. That
means, he has complete OS access to the entire DB
installation! He could read/write system catalogs without any
permission checks (SPI is only for convienience, someone can
use heap-am as well).
So in fact, he IS a superuser then. And that should be
reflected in his rights. Giving him the right would also
prevent him from doing stupid things to gain access for data
he shouldn't have, possibly corrupting you DB installation by
accident.
If that all isn't an option for you, give him his own DB
installation where he is his own superuser. There he can
develop those things and after code revision, you install the
modules in the production system.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2000-07-22 09:11 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-07-21 23:44 create function - user permissions Markus Wagner <mawagner@mail.uni-mainz.de>
2000-07-22 06:03 ` Tom Lane <tgl@sss.pgh.pa.us>
2000-07-22 09:11 ` Jan Wieck <JanWieck@t-online.de>
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