Re: Clarification on View Privileges and Operator Execution in PostgreSQL

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Ayush Vatsa <ayushvatsa1810(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Clarification on View Privileges and Operator Execution in PostgreSQL
Date: 2024-04-07 16:37:46
Message-ID: CAKFQuwYGKAeohDYe9m7ZBwto8wOc1G20dZxUJVv-aNh6St-CRg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Apr 7, 2024 at 9:32 AM Ayush Vatsa <ayushvatsa1810(at)gmail(dot)com> wrote:

> > Functions in the view are executed with the privileges of the user
> executing the query or the function owner
> So does that imply to the function associated with the operators (both
> builtin and user defined) too.
> Basically wanted to know about this -
> > Now table x will be accessed (SELECT * FROM x) with
> "postgres" privileges but who will execute the
> > underlying function inside the ( > ) operator ? Is it postgres or alex?
>
>>
>>
An operator is a function invocation with special syntax. So I expect that
sentence to apply.

If you want to confirm what the documentation says create a custom
operator/function that alex is not permitted to execute and have them query
a view defined by postgres that uses that function.

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2024-04-07 17:01:18 Re: Clarification on View Privileges and Operator Execution in PostgreSQL
Previous Message Ayush Vatsa 2024-04-07 16:32:21 Re: Clarification on View Privileges and Operator Execution in PostgreSQL