> On Feb 22, 2023, at 9:18 AM, Jeff Davis <pg...@j-davis.com> wrote: > > Another option is having some kind SECURITY NONE that would run the > code as a very limited-privilege user that can basically only access > the catalog. That would be useful for running default expressions and > the like without the definer or invoker needing to be careful. Another option is to execute under the intersection of their privileges, where both the definer and the invoker need the privileges in order for the action to succeed. That would be more permissive than the proposed SECURITY NONE, while still preventing either party from hijacking privileges of the other. — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
- Re: Non-superuser subscription owners Robert Haas
- Re: Non-superuser subscription owners Mark Dilger
- Re: Non-superuser subscription owners Robert Haas
- Re: Non-superuser subscription owners Andres Freund
- Re: Non-superuser subscription owners Robert Haas
- Re: Non-superuser subscription owners Andres Freund
- Re: Non-superuser subscription owners Robert Haas
- Re: Non-superuser subscription owners Andres Freund
- Re: Non-superuser subscription owners Robert Haas
- Re: Non-superuser subscription owners Jeff Davis
- Re: Non-superuser subscription owners Mark Dilger
- Re: Non-superuser subscription owners Jeff Davis
- Re: Non-superuser subscription owners Mark Dilger
- Re: Non-superuser subscription owners Joe Conway
- Re: Non-superuser subscription owners Robert Haas
- Re: Non-superuser subscription owners Jeff Davis
- Re: Non-superuser subscription owners Stephen Frost
- Re: Non-superuser subscription owners Jeff Davis
- Re: Non-superuser subscription owners Stephen Frost
- Re: Non-superuser subscription owners Robert Haas
- Re: Non-superuser subscription owners Jeff Davis