postgres.git / summary / log / commit / refs

commit    767d38e2c0960658251c356fedbf15c52ecb8637
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Thu Jun 05 15:29:24 2025 +0000
First released in: 18.0, 13.22, 14.19, 15.14, 16.10, 17.6

    Doc: you must own the target object to use SECURITY LABEL.
    
    For some reason this wasn't mentioned before.
    
    Author: Patrick Stählin <me@packi.ch>
    Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
    Discussion: https://postgr.es/m/931e012a-57ba-41ba-9b88-24323a46dec5@packi.ch
    Backpatch-through: 13


 doc/src/sgml/ref/security_label.sgml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/doc/src/sgml/ref/security_label.sgml b/doc/src/sgml/ref/security_label.sgml
index e5e5fb483e9..aa45c0af248 100644
--- a/doc/src/sgml/ref/security_label.sgml
+++ b/doc/src/sgml/ref/security_label.sgml
@@ -84,6 +84,10 @@ SECURITY LABEL [ FOR <replaceable class="parameter">provider</replaceable> ] ON
    based on object labels, rather than traditional discretionary access control
    (DAC) concepts such as users and groups.
   </para>
+
+  <para>
+   You must own the database object to use <command>SECURITY LABEL</command>.
+  </para>
  </refsect1>
 
  <refsect1>


[parent: 002938f15c63]