Date: Fri, 14 Dec 2007 14:11:27 -0300
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: Bill Moran <wmoran@collaborativefusion.com>,
	"Roberts, Jon" <Jon.Roberts@asurion.com>,
	"'pgsql-performance@postgresql.org'" <pgsql-performance@postgresql.org>
Subject: Re: viewing source code
Message-ID: <20071214171127.GE6269@alvh.no-ip.org>
References: 
 <1A6E6D554222284AB25ABE3229A927621129EC@nrtexcus702.int.asurion.com>
	<20071214111849.b8788ce4.wmoran@collaborativefusion.com>
	<20071214090433.08f241c1@commandprompt.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20071214090433.08f241c1@commandprompt.com>
User-Agent: Mutt/1.5.17 (2007-11-01)

Joshua D. Drake wrote:

> > > However, in the current configuration, all users with permission to
> > > log in can see all source code.  They don't have rights to execute
> > > the functions but they can see the source code for them.  Shouldn't
> > > I be able to revoke both the ability to execute and the ability to
> > > see functions?
> 
> Yes and know. If your functions are interpreted then no, I don't see
> any reason for this feature, e.g; python,perl,plpgsql,sql,ruby. I can
> read them on disk anyway.

If you have access to the files, which is not necessarily the case.
Random users, in particular, won't.

Maybe this can be done by revoking privileges to pg_proc.  I am sure it
can be made to work.  It does work for pg_auth_id, and nobody says that
"they can read the passwords from disk anyway."

-- 
Alvaro Herrera                          Developer, http://www.PostgreSQL.org/
"We're here to devour each other alive"            (Hobbes)