Table 45-27. pg_language Columns
|lanname||name||Name of the language|
|lanowner||oid||pg_authid.oid||Owner of the language|
|lanispl||bool||This is false for internal languages (such as SQL) and true for user-defined languages. Currently, pg_dump still uses this to determine which languages need to be dumped, but this might be replaced by a different mechanism in the future.|
|lanpltrusted||bool||True if this is a trusted language, which means that it is believed not to grant access to anything outside the normal SQL execution environment. Only superusers can create functions in untrusted languages.|
|lanplcallfoid||oid||pg_proc.oid||For noninternal languages this references the language handler, which is a special function that is responsible for executing all functions that are written in the particular language|
|laninline||oid||pg_proc.oid||This references a function that is responsible for executing "inline" anonymous code blocks (DO blocks). Zero if inline blocks are not supported.|
|lanvalidator||oid||pg_proc.oid||This references a language validator function that is responsible for checking the syntax and validity of new functions when they are created. Zero if no validator is provided.|
|lanacl||aclitem||Access privileges; see GRANT and REVOKE for details|
Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.
Proceed to the comment form.