From: Medi Montaseri <montaseri@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: qinghuamail-postgresqlfans@yahoo.com, postgresql-admin <pgsql-admin@postgresql.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> (raw)
In-Reply-To: <5790.1188406075@sss.pgh.pa.us>
References: <715958.65839.qm@web58103.mail.re3.yahoo.com>
<dcc563d10708290828q5d8dce04jd1d595ffa9d9775c@mail.gmail.com>
<8078a1730708290928t63620ae2h9cd3262edc40e0fe@mail.gmail.com>
<5790.1188406075@sss.pgh.pa.us>
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@sss.pgh.pa.us> wrote:
>
> "Medi Montaseri" <montaseri@gmail.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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: montaseri@gmail.com, tgl@sss.pgh.pa.us, scott.marlowe@gmail.com
Subject: Re: how to create dir using pg/plsql
In-Reply-To: <8078a1730708291350t8eb7f2fh352ef94959a45647@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox