From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-hackers@postgresql.org
Subject: Re: function body actors (was: [PERFORM] viewing source code)
Date: Fri, 21 Dec 2007 16:19:51 -0500
Message-ID: <12277.1198271991@sss.pgh.pa.us> (raw)
In-Reply-To: <20071221205619.GD3864@crankycanuck.ca>
References: <b42b73150712202109u26d05d01q4f1b8be8d29f763c@mail.gmail.com>
<26811.1198215605@sss.pgh.pa.us>
<20071221164826.GI10918@crankycanuck.ca>
<b42b73150712210948g42498150h976c0b972d632faa@mail.gmail.com>
<10257.1198263464@sss.pgh.pa.us>
<20071221205619.GD3864@crankycanuck.ca>
Andrew Sullivan <ajs@crankycanuck.ca> writes:
> Hmm; this may be exactly part of the problem, though. It seems there are
> two possible cases in play:
> 1. Protect the content in the database (in this case, function bodies)
> from _all_ users on a given server. This is a case where you want to
> protect (say) your function body from your users, because you have a
> closed-source application.
> 2. Protect the content of a field from _some_ users on a given system,
> based on the permissions they hold. This is roughly analagous to others not
> being able to look in the table I created, because I haven't GRANTed them
> permission.
I would argue that (2) is reasonably well served today by setting up
separate databases for separate users. The people who are complaining
seem to want to send out a set of functions into a hostile environment,
which is surely case (1).
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, ajs@crankycanuck.ca, pgsql-hackers@postgresql.org
Subject: Re: function body actors (was: [PERFORM] viewing source code)
In-Reply-To: <12277.1198271991@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