From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Tue, 11 Dec 2018 16:21:36 +0000 (-0500)
Subject: Doc: improve documentation about ALTER LARGE OBJECT requirements.
X-Git-Tag: REL9_6_12~68
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b48cfafd5fe74b98bc26da2e8873591971c8a800;p=postgresql

Doc: improve documentation about ALTER LARGE OBJECT requirements.

Unlike other ALTER ref pages, this one neglected to mention that
ALTER OWNER requires being a member of the new owning role.
Per bug #15546 from Stefan Kadow.

Discussion: https://postgr.es/m/15546-0558c75fd2025e7c@postgresql.org
---

diff --git a/doc/src/sgml/ref/alter_large_object.sgml b/doc/src/sgml/ref/alter_large_object.sgml
index 5748d52db1..2e9b7beab0 100644
--- a/doc/src/sgml/ref/alter_large_object.sgml
+++ b/doc/src/sgml/ref/alter_large_object.sgml
@@ -30,9 +30,15 @@ ALTER LARGE OBJECT <replaceable class="PARAMETER">large_object_oid</replaceable>
 
   <para>
    <command>ALTER LARGE OBJECT</command> changes the definition of a
-   large object. The only functionality is to assign a new owner.
-   You must be superuser or owner of the large object to use
-   <command>ALTER LARGE OBJECT</command>.
+   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 a direct or indirect member of 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>