Re: how to create dir using pg/plsql
- From: "Medi Montaseri" <montaseri(at)gmail(dot)com>
- To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, qinghuamail-postgresqlfans(at)yahoo(dot)com, postgresql-admin <pgsql-admin(at)postgresql(dot)org>
- Subject: Re: how to create dir using pg/plsql
- Date: Wed, 29 Aug 2007 13:50:04 -0700
- Message-id: <8078a1730708291350t8eb7f2fh352ef94959a45647@mail.gmail.com> <text/plain>
I see...thank you for the clarification...one more question...
How does PG protects itself from a run-away code (eg an endless loop) ? In
other words, does PG run the "untrusted" code in a seperate process?
Thanks
Medi
On 8/29/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Medi Montaseri" <montaseri(at)gmail(dot)com> writes:
> > I was under the impression that recent modern databases, like PG, allow
> you
> > to transfer control to an out-of-system (system being the DB engine)
> module
> > (shared lib, dll). That is while triggers transfer control within the
> > system, now mechanisms exists that allow you to go outside of the
> system. In
> > that context, whence the control is transferred to a C, Perl or whatever
> > language, who is to stop that function from doing anything it wants.
>
> Well, sure. Postgres calls those untrusted languages, and only lets
> database superusers use them.
>
> regards, tom lane
>
Home |
Main Index |
Thread Index