> -----Original Message-----
> From: Andrew Sullivan [mailto:ajs@crankycanuck.ca]
> Sent: Thursday, December 20, 2007 3:04 PM
> To: pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] viewing source code
>
> On Thu, Dec 20, 2007 at 01:45:08PM -0600, Roberts, Jon wrote:
> > Businesses use databases like crazy. Non-technical people write their
> own
> > code to analyze data. The stuff they write many times is as valuable as
> the
> > data itself and should be protected like the data. They don't need or
> want
> > many times to go through a middle tier to analyze data or through the
> hassle
> > to obfuscate the code.
>
> I'm not opposed to this goal, I should note. I just think that any
> proposal
> that is going to go anywhere may need to be better than the one you seem
> to
> have made.
>
> I think column-level permissions is probably something that is needed.
>
> a


Actually, PostgreSQL already has column level security for pg_stat_activity.



select * from pg_stat_activity

The current_query column shows "<insufficient privilege>" for all rows
except for rows related to my account.

It seems that we would want to do exact same thing for pg_proc.


Jon

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

On Thu, Dec 20, 2007 at 03:24:34PM -0600, Roberts, Jon wrote:
>
> Actually, PostgreSQL already has column level security for pg_stat_activity.

Not exactly. pg_stat_activity is a view.

But I think someone suggested upthread experimenting with making pg_proc
into a view, and making the real table pg_proc_real or something. This
might work.

A


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly