diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-13 13:44:03 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-13 13:44:03 +0000 |
commit | 293913568e6a7a86fd1479e1cff8e2ecb58d6568 (patch) | |
tree | fc3b469a3ec5ab71b36ea97cc7aaddb838423a0c /doc/src/sgml/ref/alter_large_object.sgml | |
parent | Initial commit. (diff) | |
download | postgresql-16-293913568e6a7a86fd1479e1cff8e2ecb58d6568.tar.xz postgresql-16-293913568e6a7a86fd1479e1cff8e2ecb58d6568.zip |
Adding upstream version 16.2.upstream/16.2
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'doc/src/sgml/ref/alter_large_object.sgml')
-rw-r--r-- | doc/src/sgml/ref/alter_large_object.sgml | 87 |
1 files changed, 87 insertions, 0 deletions
diff --git a/doc/src/sgml/ref/alter_large_object.sgml b/doc/src/sgml/ref/alter_large_object.sgml new file mode 100644 index 0000000..f427006 --- /dev/null +++ b/doc/src/sgml/ref/alter_large_object.sgml @@ -0,0 +1,87 @@ +<!-- +doc/src/sgml/ref/alter_large_object.sgml +PostgreSQL documentation +--> + +<refentry id="sql-alterlargeobject"> + <indexterm zone="sql-alterlargeobject"> + <primary>ALTER LARGE OBJECT</primary> + </indexterm> + + <refmeta> + <refentrytitle>ALTER LARGE OBJECT</refentrytitle> + <manvolnum>7</manvolnum> + <refmiscinfo>SQL - Language Statements</refmiscinfo> + </refmeta> + + <refnamediv> + <refname>ALTER LARGE OBJECT</refname> + <refpurpose>change the definition of a large object</refpurpose> + </refnamediv> + + <refsynopsisdiv> +<synopsis> +ALTER LARGE OBJECT <replaceable class="parameter">large_object_oid</replaceable> OWNER TO { <replaceable>new_owner</replaceable> | CURRENT_ROLE | CURRENT_USER | SESSION_USER } +</synopsis> + </refsynopsisdiv> + + <refsect1> + <title>Description</title> + + <para> + <command>ALTER LARGE OBJECT</command> changes the definition of a + large object. + </para> + + <para> + You must own the large object to use <command>ALTER LARGE OBJECT</command>. + To alter the owner, you must also be able to <literal>SET ROLE</literal> to + the new owning role. + (However, a superuser can alter any large object anyway.) + Currently, the only functionality is to assign a new owner, so both + restrictions always apply. + </para> + </refsect1> + + <refsect1> + <title>Parameters</title> + + <variablelist> + <varlistentry> + <term><replaceable>large_object_oid</replaceable></term> + <listitem> + <para> + OID of the large object to be altered + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><replaceable>new_owner</replaceable></term> + <listitem> + <para> + The new owner of the large object + </para> + </listitem> + </varlistentry> + </variablelist> + </refsect1> + + <refsect1> + <title>Compatibility</title> + + <para> + There is no <command>ALTER LARGE OBJECT</command> statement in the SQL + standard. + </para> + </refsect1> + + <refsect1> + <title>See Also</title> + + <simplelist type="inline"> + <member><xref linkend="largeobjects"/></member> + </simplelist> + </refsect1> + +</refentry> |