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?
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
> > to transfer control to an out-of-system (system being the DB engine)
> > (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
In response to
pgsql-admin by date
|Next:||From: Alvaro Herrera||Date: 2007-08-29 21:54:40|
|Subject: Re: how to create dir using pg/plsql|
|Previous:||From: Tom Lane||Date: 2007-08-29 19:34:58|
|Subject: Re: could not create IPv6 socket when starting Postgres server |