Re: Trusted versus untrusted Pl language
От | Steven Pousty |
---|---|
Тема | Re: Trusted versus untrusted Pl language |
Дата | |
Msg-id | CAKmB1PGk4tqV9TRNN2fXtLc7uV7vRNdrpJZDDKwKzkuaEsupGw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Trusted versus untrusted Pl language ("David G. Johnston" <david.g.johnston@gmail.com>) |
Список | pgsql-docs |
Ok David but that is not what I have heard from a lot of other people in the PostgreSQL community.
On Thu, Dec 24, 2020 at 1:26 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
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 по дате отправления: