pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Joseph Kennedy <joseph.kennedy.486@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Giovanni Biscontini <biscontini.g@es2000.it>
Cc: pgsql-general@postgresql.org
Subject: Re: PostgreSQL
Date: Mon, 03 Apr 2023 11:45:00 +0200
Message-ID: <5aec0a43c2e3d4c7be2d010b0e0684253cdb1f1e.camel@cybertec.at> (raw)
In-Reply-To: <CC59E8B4-02E1-45B1-8030-1FD44665CA7D@gmail.com>
References: <2eef5146f9836742de02d9db5cbe6cc8a4e3827d.camel@cybertec.at>
	<CC59E8B4-02E1-45B1-8030-1FD44665CA7D@gmail.com>

On Sun, 2023-04-02 at 23:21 +0200, Joseph Kennedy wrote:
> I have one more question on this topic regarding Row Level Security. 
> 
> I would like to hide some rows for users who should have full rights to database
> eg. create Index, drop table, create tabel etc. but e.g.  create index can be
> done by owner or superusers but they are bypassed by Row Level Security. 
> 
> Is possible to use RLS for users who should have full rights to database ?

If "full rights" implies dropping tables, the user must either be the owner
of these tables or a superuser.  You cannot use Row Level Security with a
superuser.  You can use ALTER TABLE ... FORCE ROW LEVEL SECURITY, so that
Row Level Security applies to the table owner as well, but you cannot keep
the owner from disabling that setting.

Yours,
Laurenz Albe





view thread (68+ messages)

Message-ID: <5aec0a43c2e3d4c7be2d010b0e0684253cdb1f1e.camel@cybertec.at>
Permalink:  ../5aec0a43c2e3d4c7be2d010b0e0684253cdb1f1e.camel@cybertec.at/
Also on:    postgresql.org/message-id/5aec0a43c2e3d4c7be2d010b0e0684253cdb1f1e.camel@cybertec.at

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: laurenz.albe@cybertec.at, joseph.kennedy.486@gmail.com, sfrost@snowman.net, biscontini.g@es2000.it
  Subject: Re: PostgreSQL
  In-Reply-To: <5aec0a43c2e3d4c7be2d010b0e0684253cdb1f1e.camel@cybertec.at>
  References: <2eef5146f9836742de02d9db5cbe6cc8a4e3827d.camel@cybertec.at> <CC59E8B4-02E1-45B1-8030-1FD44665CA7D@gmail.com> <5aec0a43c2e3d4c7be2d010b0e0684253cdb1f1e.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox