mirror of
https://github.com/postgres/postgres.git
synced 2025-12-21 05:21:08 +03:00
3cdf7502f8
Update the reference pages for various ALTER commands that mentioned that you must be a member of role that will be the new owner to instead say that you must be able to SET ROLE to the new owner. Update ddl.sgml's generate statement on this topic along similar lines. Likewise, update CREATE SCHEMA and CREATE DATABASE, which have options to specify who will own the new objects, to say that you must be able to SET ROLE to the role that will own them. Finally, update the documentation for the GRANT statement itself with some general principles about how the SET option works and how it can be used. Patch by me, reviewed (but not fully endorsed) by Noah Misch. Discussion: http://postgr.es/m/CA+TgmoZk6VB3DQ83+DO5P_HP=M9PQAh1yj-KgeV30uKefVaWDg@mail.gmail.com
88 lines
2.0 KiB
Plaintext
88 lines
2.0 KiB
Plaintext
<!--
|
|
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>
|