mirror of
https://github.com/postgres/postgres.git
synced 2025-11-06 07:49:08 +03:00
Update documentation to reflect that standard PLs are now extensions.
Recommend use of CREATE EXTENSION rather than plain CREATE LANGUAGE where relevant. Encourage PL authors to provide extension wrappers for their PLs.
This commit is contained in:
@@ -37,6 +37,21 @@ CREATE [ OR REPLACE ] [ TRUSTED ] [ PROCEDURAL ] LANGUAGE <replaceable class="pa
|
||||
defined in this new language.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
As of <productname>PostgreSQL</productname> 9.1, most procedural
|
||||
languages have been made into <quote>extensions</>, and should
|
||||
therefore be installed with <xref linkend="sql-createextension">
|
||||
not <command>CREATE LANGUAGE</command>. Direct use of
|
||||
<command>CREATE LANGUAGE</command> should now be confined to
|
||||
extension installation scripts. If you have a <quote>bare</>
|
||||
language in your database, perhaps as a result of an upgrade,
|
||||
you can convert it to an extension using
|
||||
<literal>CREATE EXTENSION <replaceable>langname</> FROM
|
||||
unpackaged</literal>.
|
||||
</para>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
<command>CREATE LANGUAGE</command> effectively associates the
|
||||
language name with handler function(s) that are responsible for executing
|
||||
|
||||
Reference in New Issue
Block a user