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 f4a9c9e2a52443af1243107a7051f652a9cddc51..356f8a8eabf4db3edc5e89311d32fac2ca3497a1 100644 (file)
--- 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 large_object_oid
 
   
    ALTER LARGE OBJECT 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
-   ALTER LARGE OBJECT.
+   large object.
+  
+
+  
+   You must own the large object to use ALTER LARGE OBJECT.
+   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.