So your suggestion is first to come up with a query that dynamically checks
permissions and create a view for it. Secondly, change pgAdmin to reference
this view in place of pg_proc. Actually, it should be extended to all
objects in the database, not just pg_proc. If you don't have this
dictionary role, you shouldn't be able to look at any of the objects in the
database unless you own the object or have been granted rights to the
object.
I don't know the information_schema that well so I don't know if this is
something that should sit on top of PostgreSQL with views and then make
subsequent changes to pgAdmin or if the database itself needs to change to
handle this.
Jon
> -----Original Message-----
> From: Alvaro Herrera [mailto:alvherre@commandprompt.com]
> Sent: Wednesday, December 19, 2007 9:56 AM
> To: Roberts, Jon
> Cc: 'Trevor Talbot'; Joshua D. Drake; Kris Jurka; Merlin Moncure; Jonah H.
> Harris; Bill Moran; pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] viewing source code
>
> Roberts, Jon escribió:
>
> > The more I thought about a counter proposal to put views on pg_proc, I
> > realized that isn't feasible either. It would break functionality of
> > pgAdmin because users couldn't view their source code with the tool.
>
> What's wrong with patching pgAdmin?
>
> --
> Alvaro Herrera
> http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support