Re: Trusted versus untrusted Pl language - Mailing list pgsql-docs

From David G. Johnston
Subject Re: Trusted versus untrusted Pl language
Date
Msg-id CAKFQuwacAd2_KhuQiZw-C+7WPkCf3to3B9jSe_WOqa_K8rNc9w@mail.gmail.com
Whole thread Raw
In response to Re: Trusted versus untrusted Pl language  (Steven Pousty <steve.pousty@gmail.com>)
Responses Re: Trusted versus untrusted Pl language
List pgsql-docs
On Thu, Dec 24, 2020 at 1:01 PM Steven Pousty <steve.pousty@gmail.com> wrote:
The SQL I am talking about is this:
UPDATE pg_language SET lanpltrusted = true WHERE lanname LIKE 'plr'; 

You seem to be missing the point.  The language is either trusted, or it's not.  Modifying the catalogs is not part of a "good flow", ever.  In short, "don't use trusted languages ever".  If a specific requirement can only be implemented using a trusted language maybe there is a reason to use it - in development and production (if your DBA will let you) - but more likely you are better off writing an out-of-database client application and doing the "trusted" stuff there.

David J.

pgsql-docs by date:

Previous
From: Steven Pousty
Date:
Subject: Re: Trusted versus untrusted Pl language
Next
From: Steven Pousty
Date:
Subject: Re: Trusted versus untrusted Pl language