So you are saying I need to create a view per user to achieve this? That isn't practical for an enterprise level database. I'm basically suggesting row level security that would be implemented for a system table and then RLS could be used for user defined tables too. Jon > -----Original Message----- > From: Alvaro Herrera [mailto:alvherre@xxxxxxxxxxxxxxxxx] > Sent: Tuesday, December 18, 2007 12:27 PM > To: Roberts, Jon > Cc: 'Kris Jurka'; Merlin Moncure; Jonah H. Harris; Bill Moran; Joshua D. > Drake; pgsql-performance@xxxxxxxxxxxxxx > Subject: Re: viewing source code > > Roberts, Jon escribió: > > > Revoking pg_proc isn't good for users that shouldn't see other's code > but > > still need to be able to see their own code. > > So create a view on top of pg_proc restricted by current role, and grant > select on that to users. > > -- > Alvaro Herrera > http://www.CommandPrompt.com/ > The PostgreSQL Company - Command Prompt, Inc. ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
