On 6/5/25 4:21 PM, Laurenz Albe wrote:
+
+
+ You must own the database object to use the SECURITY
LABEL.
+
Wouldn't it be more accurate to say that you have to be a member of the owning
role?
But perhaps that would be complicated enough to confuse many users.
We're calling
On Thu, 2025-06-05 at 11:19 -0400, Tom Lane wrote:
> Laurenz Albe writes:
> > On Thu, 2025-06-05 at 15:29 +0200, Patrick Stählin wrote:
> > > I noticed that we don't document that you need to own the object being
> > > modified by SECURITY LABEL.
>
> Yeah, clearly a documentation oversight.
>
>
Laurenz Albe writes:
> On Thu, 2025-06-05 at 15:29 +0200, Patrick Stählin wrote:
>> I noticed that we don't document that you need to own the object being
>> modified by SECURITY LABEL.
Yeah, clearly a documentation oversight.
> Wouldn't it be more accurate to say that you have to be a member o
On Thu, 2025-06-05 at 15:29 +0200, Patrick Stählin wrote:
> Hi,
>
> I noticed that we don't document that you need to own the object being
> modified by SECURITY LABEL.
>
> Page: https://www.postgresql.org/docs/current/sql-security-label.html
>
> I've attached a patch that would have answered t
Hi,
I noticed that we don't document that you need to own the object being
modified by SECURITY LABEL.
Page: https://www.postgresql.org/docs/current/sql-security-label.html
I've attached a patch that would have answered that question (for me)
without diving into the code.
Thanks,
PatrickFr
