Date: Tue, 18 Dec 2007 15:52:23 -0300
From: Alvaro Herrera <alvherre@commandprompt.com>
To: "Roberts, Jon" <Jon.Roberts@asurion.com>
Cc: "'Kris Jurka'" <books@ejurka.com>, Merlin Moncure <mmoncure@gmail.com>,
	"Jonah H. Harris" <jonah.harris@gmail.com>,
	Bill Moran <wmoran@collaborativefusion.com>,
	"Joshua D. Drake" <jd@commandprompt.com>, pgsql-performance@postgresql.org
Subject: Re: viewing source code
Message-ID: <20071218185223.GD8088@alvh.no-ip.org>
References: 
 <1A6E6D554222284AB25ABE3229A92762112A25@nrtexcus702.int.asurion.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <1A6E6D554222284AB25ABE3229A92762112A25@nrtexcus702.int.asurion.com>
User-Agent: Mutt/1.5.17 (2007-11-01)

Roberts, Jon escribió:
> So you are saying I need to create a view per user to achieve this?  That
> isn't practical for an enterprise level database.

No -- that would be quite impractical indeed.  I'm talking about
something like

revoke all privileges on pg_proc from public;
create view limited_pg_proc
as select * from pg_proc
where proowner = (select oid from pg_authid where rolname = current_user);
grant select on limited_pg_proc to public;

Of course, it is only a rough sketch.  It needs to be improved in a
number of ways.  But it shows that even with pure SQL the solution is
not far; with backend changes it is certainly doable (for example invent
a separate "view source" privilege for functions).

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.