| From: | Steve Chavez <steve(at)supabase(dot)io> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add SECURITY_INVOKER_VIEWS option to CREATE DATABASE |
| Date: | 2026-01-28 20:43:54 |
| Message-ID: | CAGRrpzZmgGoB6upQLjSO3PtPn=Y6Wg+ZA7Qig4EFYwiFMnn0Eg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
But that is a property of just regular views not necessarily
security_barrier right? i.e. "to be able to hide certain columns".
> Please don't top-post.
My bad, to be honest I don't understand how I can reply to different
paragraphs in a more structured way.
Are there guidelines/examples on the pg docs about this rule?
Best regards,
Steve
On Wed, 28 Jan 2026 at 15:28, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> On Wed, 2026-01-28 at 14:19 -0500, Steve Chavez wrote:
> > CMIIW, but wasn't security_barrier a mechanism to do RLS before actual
> RLS (policies) were introduced? So in a way aren't they superseded by RLS?
>
> I wouldn't say so.
>
> Creating a view that allows a user to see only certain columns of a table
> is something quite different from restricting the rows a user can operate
> on.
>
> Yours,
> Laurenz Albe
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2026-01-28 20:49:53 | Re: Mystery with REVOKE PRIVILEGE |
| Previous Message | Viktor Holmberg | 2026-01-28 20:33:21 | Re: ON CONFLICT DO SELECT (take 3) |