I'm not familiar at all with pg_read_file. Is it wide open so a user can
read any file they want? Can you not lock it down like utl_file and
directories in Oracle?


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/

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

Roberts, Jon escribió:
> I'm not familiar at all with pg_read_file. Is it wide open so a user can
> read any file they want? Can you not lock it down like utl_file and
> directories in Oracle?

That function is restricted to superusers.

--
Alvaro Herrera Developer, http://www.PostgreSQL.org/
"The Postgresql hackers have what I call a "NASA space shot" mentality.
Quite refreshing in a world of "weekend drag racer" developers."
(Scott Marlowe)

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq