↑↓ 选择↵ 打开⌫ 切换范围完整搜索

PG.CENTER 连接 PostgreSQL 文档、百科与生态知识。由 Pigsty 维护。

Wiki / 过程语言

plpgsql

PL/pgSQL procedural language

当前阅读 PG 18·选择有来源记录的版本

此版本暂无所选语言的定义,以下显示原始英文内容。

Kind
Bundled procedural-language variant
Family
PL/pgSQL
Trusted
t
Handler
plpgsql_call_handler
Inline handler
plpgsql_inline_handler
Validator
plpgsql_validator
Library
$libdir/plpgsql
Default version
1.0
Module pathname
$libdir/plpgsql
Comment
PL/pgSQL procedural language
aliases
未知
manual path
/docs/18/plpgsql-overview.html
signature
未知

版本定义 PG 18

41.1. Overview

PL/pgSQL is a loadable procedural language for the PostgreSQL database system. The design goals of PL/pgSQL were to create a loadable procedural language that

  • can be used to create functions, procedures, and triggers,

  • adds control structures to the SQL language,

  • can perform complex computations,

  • inherits all user-defined types, functions, procedures, and operators,

  • can be defined to be trusted by the server,

  • is easy to use.

Functions created with PL/pgSQL can be used anywhere that built-in functions could be used. For example, it is possible to create complex conditional computation functions and later use them to define operators or use them in index expressions.

In PostgreSQL 9.0 and later, PL/pgSQL is installed by default. However it is still a loadable module, so especially security-conscious administrators could choose to remove it.

41.1.1. Advantages of Using PL/pgSQL

SQL is the language PostgreSQL and most other relational databases use as query language. It's portable and easy to learn. But every SQL statement must be executed individually by the database server.

That means that your client application must send each query to the database server, wait for it to be processed, receive and process the results, do some computation, then send further queries to the server. All this incurs interprocess communication and will also incur network overhead if your client is on a different machine than the database server.

With PL/pgSQL you can group a block of computation and a series of queries inside the database server, thus having the power of a procedural language and the ease of use of SQL, but with considerable savings of client/server communication overhead.

  • Extra round trips between client and server are eliminated

  • Intermediate results that the client does not need do not have to be marshaled or transferred between server and client

  • Multiple rounds of query parsing can be avoided

This can result in a considerable performance increase as compared to an application that does not use stored functions.

Also, with PL/pgSQL you can use all the data types, operators and functions of SQL.

41.1.2. Supported Argument and Result Data Types

Functions written in PL/pgSQL can accept as arguments any scalar or array data type supported by the server, and they can return a result of any of these types. They can also accept or return any composite type (row type) specified by name. It is also possible to declare a PL/pgSQL function as accepting record, which means that any composite type will do as input, or as returning record, which means that the result is a row type whose columns are determined by specification in the calling query, as discussed in Section 7.2.1.4.

PL/pgSQL functions can be declared to accept a variable number of arguments by using the VARIADIC marker. This works exactly the same way as for SQL functions, as discussed in Section 36.5.6.

PL/pgSQL functions can also be declared to accept and return the polymorphic types described in Section 36.2.5, thus allowing the actual data types handled by the function to vary from call to call. Examples appear in Section 41.3.1.

PL/pgSQL functions can also be declared to return a “set” (or table) of any data type that can be returned as a single instance. Such a function generates its output by executing RETURN NEXT for each desired element of the result set, or by using RETURN QUERY to output the result of evaluating a query.

Finally, a PL/pgSQL function can be declared to return void if it has no useful return value. (Alternatively, it could be written as a procedure in that case.)

PL/pgSQL functions can also be declared with output parameters in place of an explicit specification of the return type. This does not add any fundamental capability to the language, but it is often convenient, especially for returning multiple values. The RETURNS TABLE notation can also be used in place of RETURNS SETOF.

Specific examples appear in Section 41.3.1 and Section 41.6.1.

比较版本

完整来源事实

attributes

{"comment":"PL/pgSQL procedural language","default_version":"1.0","family":"PL/pgSQL","handler":"plpgsql_call_handler","inline_handler":"plpgsql_inline_handler","kind":"Bundled procedural-language variant","library":"$libdir/plpgsql","module_pathname":"$libdir/plpgsql","trusted":"t","validator":"plpgsql_validator"}

source files

{"src/pl/plpgsql/src/plpgsql--1.0.sql":"f4e7e05438808ac0da0b3801397d16e36102969af7e2ffc982def5b7524fb557","src/pl/plpgsql/src/plpgsql.control":"9457c3f51d6bdfab93f13080d177795a9274c025e378fb613218342e3a3c7b45"}

来源引用

完整定义与证据 JSON

定义来源

center · PostgreSQL 18 · 555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f

正文语言: en · 555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f