DO
execute an anonymous code block
English manual coverage begins with PostgreSQL 6.4. Source history and runtime observations have their own recorded version boundaries.
Reading PG 18·Select a recorded version
- anchor
- SQL-DO
- file
- sql-do.html
- lang
- en
- name
- DO
- purpose
- execute an anonymous code block
- purpose zh
- 执行匿名代码块
- sections same as
- Unknown
- slug
- 18
- synopsis html
- DO [ LANGUAGE <em class="replaceable"><code>lang_name</code></em> ] <em class="replaceable"><code>code</code></em>
- synopsis text
- DO [ LANGUAGE lang_name ] code
Syntax
DO [ LANGUAGE lang_name ] codeSyntax diagrams
Read left to right. Branches are choices, bypasses are optional, loops repeat. Select an underlined parameter to open its rule.
Definition PG 18
DO [ LANGUAGE lang_name ] code
Description
DO executes an anonymous code block, or in other
words a transient anonymous function in a procedural language.
The code block is treated as though it were the body of a function
with no parameters, returning void. It is parsed and
executed a single time.
The optional LANGUAGE clause can be written either
before or after the code block.
Parameters
codeThe procedural language code to be executed. This must be specified as a string literal, just as in
CREATE FUNCTION. Use of a dollar-quoted literal is recommended.lang_nameThe name of the procedural language the code is written in. If omitted, the default is
plpgsql.
Notes
The procedural language to be used must already have been installed
into the current database by means of CREATE EXTENSION.
plpgsql is installed by default, but other languages are not.
The user must have USAGE privilege for the procedural
language, or must be a superuser if the language is untrusted.
This is the same privilege requirement as for creating a function
in the language.
If DO is executed in a transaction block, then the
procedure code cannot execute transaction control statements. Transaction
control statements are only allowed if DO is executed in
its own transaction.
Examples
Grant all privileges on all views in schema public to
role webuser:
DO $$
DECLARE r record;
BEGIN
FOR r IN SELECT table_schema, table_name FROM information_schema.tables
WHERE table_type = 'VIEW' AND table_schema = 'public'
LOOP
EXECUTE 'GRANT ALL ON ' || quote_ident(r.table_schema) || '.' || quote_ident(r.table_name) || ' TO webuser';
END LOOP;
END$$;
Compatibility
There is no DO statement in the SQL standard.
See Also
CREATE LANGUAGECompare versions
Complete source facts
documentation revision
{"inputs":[{"file":"sql-do.html","kind":"same-version-reviewed-manual","locale":"en","sha256":"9a7e6ac5693fc6aab66c1f57d14eaa139c20b5b326ee49ceaf0696c60e3f1b94","version":"18.7"},{"file":"sql-do.html","kind":"same-version-reviewed-manual","locale":"zh-Hans","sha256":"c00b3f08a94808c4a141643fde64463e026cf95fef018dabf9d7907ea3b11df9","version":"18.7"}],"release":"18.7","runtime_remeasured":false,"source_revision":"pgdoc:b9f0e7232f60f380d642ac9b99226606c254b552"}Source references
Full definition and evidence JSON
Definition sources
center · PostgreSQL 18 · wiki-repair-20261023:39624b539264e3bf743e408e29569a41aa906e1cf1ad1072ffa416ce1f002654
Text language: en · wiki-repair-20261023:39624b539264e3bf743e408e29569a41aa906e1cf1ad1072ffa416ce1f002654