Re: viewing source code
От | Roberts, Jon |
---|---|
Тема | Re: viewing source code |
Дата | |
Msg-id | 1A6E6D554222284AB25ABE3229A92762112A25@nrtexcus702.int.asurion.com обсуждение исходный текст |
Ответ на | viewing source code ("Roberts, Jon" <Jon.Roberts@asurion.com>) |
Ответы |
Re: viewing source code
Re: viewing source code |
Список | pgsql-performance |
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@commandprompt.com] > 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@postgresql.org > Subject: Re: [PERFORM] 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.
В списке pgsql-performance по дате отправления: