4 The catalog pg_language registers languages in which you can write
5 functions or stored procedures. See CREATE LANGUAGE and Chapter 40 for
6 more information about language handlers.
8 Table 52.29. pg_language Columns
22 lanowner oid (references pg_authid.oid)
28 This is false for internal languages (such as SQL) and true for
29 user-defined languages. Currently, pg_dump still uses this to determine
30 which languages need to be dumped, but this might be replaced by a
31 different mechanism in the future.
35 True if this is a trusted language, which means that it is believed not
36 to grant access to anything outside the normal SQL execution
37 environment. Only superusers can create functions in untrusted
40 lanplcallfoid oid (references pg_proc.oid)
42 For noninternal languages this references the language handler, which
43 is a special function that is responsible for executing all functions
44 that are written in the particular language. Zero for internal
47 laninline oid (references pg_proc.oid)
49 This references a function that is responsible for executing “inline”
50 anonymous code blocks (DO blocks). Zero if inline blocks are not
53 lanvalidator oid (references pg_proc.oid)
55 This references a language validator function that is responsible for
56 checking the syntax and validity of new functions when they are
57 created. Zero if no validator is provided.
61 Access privileges; see Section 5.8 for details