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

Re: viewing source code

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
Cc: "'Jonah H(dot) Harris'" <jonah(dot)harris(at)gmail(dot)com>, Bill Moran <wmoran(at)collaborativefusion(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: viewing source code
Date: 2007-12-17 16:13:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Roberts, Jon wrote:
> Alvaro Herrera pointed out that pg_read_file requires superuser access which
> these users won't have so revoking access to the function code should be
> possible.
> Joshua D. Drake suggested revoking pg_proc but that isn't the source code,
> it just has the definition of the functions.  

Actually I suggested using a obfuscation module.

> If it isn't a feature today, what table has the source code in it?  Maybe I
> can revoke that.

If your pl is perl or plpgsql it will be in the prosrc (pro_src?) column 
in pg_proc.

Joshua D. Drake

> Jon
>> -----Original Message-----
>> From: Jonah H. Harris [mailto:jonah(dot)harris(at)gmail(dot)com]
>> Sent: Friday, December 14, 2007 3:04 PM
>> To: Bill Moran
>> Cc: Joshua D. Drake; Roberts, Jon; pgsql-performance(at)postgresql(dot)org
>> Subject: Re: [PERFORM] viewing source code
>> On Dec 14, 2007 2:03 PM, Bill Moran <wmoran(at)collaborativefusion(dot)com>
>> wrote:
>>> I disagree here.  If they're connecting remotely to PG, they have no
>>> direct access to the disk.
>> pg_read_file?
>> --
>> Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
>> EnterpriseDB Corporation                | fax: 732.331.1301
>> 499 Thornall Street, 2nd Floor          | jonah(dot)harris(at)enterprisedb(dot)com
>> Edison, NJ 08837                        |
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

In response to

pgsql-performance by date

Next:From: H. HallDate: 2007-12-17 17:53:48
Subject: Re: update 600000 rows
Previous:From: Kevin GrittnerDate: 2007-12-17 15:45:43
Subject: Re: VACUUM FREEZE output more than double input

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