Movatterモバイル変換


[0]ホーム

URL:



Facebook
Postgres Pro
Facebook
Downloads
40.1. Installing Procedural Languages
Prev UpChapter 40. Procedural LanguagesHome Next

40.1. Installing Procedural Languages#

A procedural language must beinstalled into each database where it is to be used. But procedural languages installed in the databasetemplate1 are automatically available in all subsequently created databases, since their entries intemplate1 will be copied byCREATE DATABASE. So the database administrator can decide which languages are available in which databases and can make some languages available by default if desired.

For the languages supplied with the standard distribution, it is only necessary to executeCREATE EXTENSIONlanguage_name to install the language into the current database. The manual procedure described below is only recommended for installing languages that have not been packaged as extensions.

Manual Procedural Language Installation

A procedural language is installed in a database in five steps, which must be carried out by a database superuser. In most cases the required SQL commands should be packaged as the installation script of anextension, so thatCREATE EXTENSION can be used to execute them.

  1. The shared object for the language handler must be compiled and installed into an appropriate library directory. This works in the same way as building and installing modules with regular user-defined C functions does; seeSection 36.10.5. Often, the language handler will depend on an external library that provides the actual programming language engine; if so, that must be installed as well.

  2. The handler must be declared with the command

    CREATE FUNCTIONhandler_function_name()    RETURNS language_handler    AS 'path-to-shared-object'    LANGUAGE C;

    The special return type oflanguage_handler tells the database system that this function does not return one of the definedSQL data types and is not directly usable inSQL statements.

  3. Optionally, the language handler can provide aninline handler function that executes anonymous code blocks (DO commands) written in this language. If an inline handler function is provided by the language, declare it with a command like

    CREATE FUNCTIONinline_function_name(internal)    RETURNS void    AS 'path-to-shared-object'    LANGUAGE C;

  4. Optionally, the language handler can provide avalidator function that checks a function definition for correctness without actually executing it. The validator function is called byCREATE FUNCTION if it exists. If a validator function is provided by the language, declare it with a command like

    CREATE FUNCTIONvalidator_function_name(oid)    RETURNS void    AS 'path-to-shared-object'    LANGUAGE C STRICT;

  5. Finally, the PL must be declared with the command

    CREATE [TRUSTED] LANGUAGElanguage_name    HANDLERhandler_function_name    [INLINEinline_function_name]    [VALIDATORvalidator_function_name] ;

    The optional key wordTRUSTED specifies that the language does not grant access to data that the user would not otherwise have. Trusted languages are designed for ordinary database users (those without superuser privilege) and allows them to safely create functions and procedures. Since PL functions are executed inside the database server, theTRUSTED flag should only be given for languages that do not allow access to database server internals or the file system. The languagesPL/pgSQL,PL/Tcl, andPL/Perl are considered trusted; the languagesPL/TclU,PL/PerlU, andPL/PythonU are designed to provide unlimited functionality and shouldnot be marked trusted.

Example 40.1 shows how the manual installation procedure would work with the languagePL/Perl.

Example 40.1. Manual Installation ofPL/Perl

The following command tells the database server where to find the shared object for thePL/Perl language's call handler function:

CREATE FUNCTION plperl_call_handler() RETURNS language_handler AS    '$libdir/plperl' LANGUAGE C;

PL/Perl has an inline handler function and a validator function, so we declare those too:

CREATE FUNCTION plperl_inline_handler(internal) RETURNS void AS    '$libdir/plperl' LANGUAGE C STRICT;CREATE FUNCTION plperl_validator(oid) RETURNS void AS    '$libdir/plperl' LANGUAGE C STRICT;

The command:

CREATE TRUSTED LANGUAGE plperl    HANDLER plperl_call_handler    INLINE plperl_inline_handler    VALIDATOR plperl_validator;

then defines that the previously declared functions should be invoked for functions and procedures where the language attribute isplperl.


In a defaultPostgres Pro installation, the handler for thePL/pgSQL language is built and installed into thelibrary directory; furthermore, thePL/pgSQL language itself is installed in all databases. IfTcl support is configured in, the handlers forPL/Tcl andPL/TclU are built and installed in the library directory, but the language itself is not installed in any database by default. Likewise, thePL/Perl andPL/PerlU handlers are built and installed if Perl support is configured, and thePL/PythonU handler is installed if Python support is configured, but these languages are not installed by default.


Prev Up Next
Chapter 40. Procedural Languages Home Chapter 41. PL/pgSQLSQL Procedural Language
pdfepub
Go to Postgres Pro Standard 17
By continuing to browse this website, you agree to the use of cookies. Go toPrivacy Policy.

[8]ページ先頭

©2009-2025 Movatter.jp