Re: viewing source code - Mailing list pgsql-performance

From Roberts, Jon
Subject Re: viewing source code
Date
Msg-id 1A6E6D554222284AB25ABE3229A92762112A00@nrtexcus702.int.asurion.com
Whole thread Raw
In response to viewing source code  ("Roberts, Jon" <Jon.Roberts@asurion.com>)
Responses Re: viewing source code  ("Merlin Moncure" <mmoncure@gmail.com>)
Re: viewing source code  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-performance
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.

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


Jon
> -----Original Message-----
> From: Jonah H. Harris [mailto:jonah.harris@gmail.com]
> Sent: Friday, December 14, 2007 3:04 PM
> To: Bill Moran
> Cc: Joshua D. Drake; Roberts, Jon; pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] viewing source code
>
> On Dec 14, 2007 2:03 PM, Bill Moran <wmoran@collaborativefusion.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.harris@enterprisedb.com
> Edison, NJ 08837                        | http://www.enterprisedb.com/

pgsql-performance by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: libgcc double-free, backend won't die
Next
From: "Merlin Moncure"
Date:
Subject: Re: viewing source code