Skip site navigation (1) Skip section navigation (2)

Re: viewing source code

From: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
To: 'Andrew Sullivan' <ajs(at)crankycanuck(dot)ca>, pgsql-performance(at)postgresql(dot)org
Subject: Re: viewing source code
Date: 2007-12-20 21:24:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance

> -----Original Message-----
> From: Andrew Sullivan [mailto:ajs(at)crankycanuck(dot)ca]
> Sent: Thursday, December 20, 2007 3:04 PM
> To: pgsql-performance(at)postgresql(dot)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.



pgsql-performance by date

Next:From: Andrew SullivanDate: 2007-12-20 21:29:04
Subject: Re: viewing source code
Previous:From: Andrew SullivanDate: 2007-12-20 21:04:13
Subject: Re: viewing source code

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group