From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Steven Pousty <steve.pousty@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Trusted versus untrusted Pl language
Date: Wed, 23 Dec 2020 19:49:22 -0500
Message-ID: <20201224004922.GB13055@momjian.us> (raw)
In-Reply-To: <748034.1608770296@sss.pgh.pa.us>
References: <160875505390.674.9084620641912624635@wrigleys.postgresql.org>
<20201223224140.GA13055@momjian.us>
<CAKmB1PFuxkvA5-wD7KkW0yLp_4-+ieeVz7a2C5udg+GQVy9mgA@mail.gmail.com>
<748034.1608770296@sss.pgh.pa.us>
On Wed, Dec 23, 2020 at 07:38:16PM -0500, Tom Lane wrote:
> Steven Pousty <steve.pousty@gmail.com> writes:
> > 3. An example of how to make a pre-installed untrusted langue into a
> > trusted language
>
> Under what circumstances would that be a good idea?
>
> I can't imagine that we'd really want to recommend end users doing
> that, but an example would surely be taken as a recommendation
> that it's okay to do it.
Right. The language has to provide some sandbox environment for us to
consider it safe, e.g. Perl, but not Python. PL/pgSQL is safe since it
doesn't have any interface to external resources.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
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-docs@postgresql.org
Cc: bruce@momjian.us, tgl@sss.pgh.pa.us, steve.pousty@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Trusted versus untrusted Pl language
In-Reply-To: <20201224004922.GB13055@momjian.us>
* 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