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 <[EMAIL PROTECTED]> wrote: > > "Medi Montaseri" <[EMAIL PROTECTED]> 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 >
