Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pQ2h8-0005Ql-Hl for pgsql-general@arkaria.postgresql.org; Thu, 09 Feb 2023 08:54:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pQ2h7-0002vU-B2 for pgsql-general@arkaria.postgresql.org; Thu, 09 Feb 2023 08:54:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pQ2h6-0002ub-UC for pgsql-general@lists.postgresql.org; Thu, 09 Feb 2023 08:54:17 +0000 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pQ2h4-0008Ib-Pj for pgsql-general@postgresql.org; Thu, 09 Feb 2023 08:54:15 +0000 Received: by mail-wm1-x329.google.com with SMTP id k8-20020a05600c1c8800b003dc57ea0dfeso3363344wms.0 for ; Thu, 09 Feb 2023 00:54:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=Bd9/vBXss1eZtGCBrl5FQ4anbmGAhTRUF7K2MwH/CrU=; b=EKQze+2BV+x5Z5Ndt2IR4tftboVJdyIqqCAmHuDr3AxSrPtGFqoxdnyzGt8arS6JcP 9naAp7e4nbGp+Q8ZNy82ElumoLI+WdMwuBgbEkvqkOYJCWby6GiX4PpYTPDYrwnIYjoJ +EoVU8g7KZDPaZzpXGwdjvNC8CENqAw/4i03BOqjVkruJx/UB8dc1mWJ7Nb+WqITY+RC RVXspO6QdbdR5hp7H5c5iFzKGhv+0aRBqb88fOgFzVR2bXIWbi40/r/D1oZ+wvnxVZMz uW+JguLs7rFZ7xmiC20PUc/PmC1cTri8Ebg7+tme731L0ytbrlgPrL9AVNGV/fldbq7T LTcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Bd9/vBXss1eZtGCBrl5FQ4anbmGAhTRUF7K2MwH/CrU=; b=Mp1BVsWCJDtoKx0ioAMyHmhL8rYsveGv1jXNCgKBPaLyCmYsiTV6nQlHt/HwKho+vp SzBN02nz7Ed2NL46oicTH+GSCNnzHGo9Jop9sCjF0RLmYmNMC3SZ8Tlurl6jJNT/CFIJ 7eIfSGaOKZlmNT0KDmWsR9gTuoorTWc3cK6L2R3ZOUCUEoLdaZ0LsjuexbHiSg3s71vB yAuZyViFw5wlGEt6AcdB6uA1B8dcMLdp+IPgTo8Jt3sWIBOZVm2ypKu1doFzxSmbRdyG 7/P7935sjJg39RwgxH2Nfn9rI5dvJ/EXYhR7zVuJ8AhP09p4wcpEmwCkVdY99a3Nql4T uBVA== X-Gm-Message-State: AO0yUKU/Q6xk9vJOJk4zK2Y8s3lL/MJHJnj8uBlOnSJh7VCdFnCv1RbV uMt/o0DdOcN2auvhMDiAgZY= X-Google-Smtp-Source: AK7set8Y6z+feV2YxzJ2P5bs8JcFf2y1uuwq3JF+99tXtzbZjk4YJzyR8uhhKkDdyG2v0nil09vjYg== X-Received: by 2002:a05:600c:4d16:b0:3dc:5093:3457 with SMTP id u22-20020a05600c4d1600b003dc50933457mr9512388wmp.10.1675932852317; Thu, 09 Feb 2023 00:54:12 -0800 (PST) Received: from smtpclient.apple ([89.171.50.130]) by smtp.gmail.com with ESMTPSA id z5-20020a5d6405000000b002c3f0ea831dsm708880wru.15.2023.02.09.00.54.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 09 Feb 2023 00:54:11 -0800 (PST) Content-Type: multipart/alternative; boundary=Apple-Mail-CC36B227-A781-455E-846A-8334973818CC Content-Transfer-Encoding: 7bit From: Joseph Kennedy Mime-Version: 1.0 (1.0) Subject: Re: PostgreSQL Date: Thu, 9 Feb 2023 09:54:00 +0100 Message-Id: References: Cc: Laurenz Albe , Giovanni Biscontini , pgsql-general@postgresql.org In-Reply-To: To: Stephen Frost X-Mailer: iPhone Mail (20D47) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail-CC36B227-A781-455E-846A-8334973818CC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable As I wtote, I would like restrict access to sensitive or restricted informat= ion for some users (eg. hide data of one or more clients for some database u= sers). My question is: do you know some other solution to do that ?=20 Some 3rd party solution eg. similar to pgpool or something else ? Maybe RLS is the beat solution for me.=20 Thank you for your suggestions.=20 > Wiadomo=C5=9B=C4=87 napisana przez Stephen Frost w dn= iu 08.02.2023, o godz. 01:36: >=20 > =EF=BB=BFGreetings, >=20 > * Joseph Kennedy (joseph.kennedy.486@gmail.com) wrote: >> Thank you Laurenz, I just wanted to make sure.=20 >>=20 >> Do you know any alternative solution to RLS ? >=20 > ... to do what? If you want to limit the set of rows that a given user > can see, RLS is how to do that. If you want to limit the schemas or > tables that a user can see, that isn't possible in PG today (though > there was some interest a while back in making that work via RLS on the > catalogs which you might be able to find). >=20 > Thanks, >=20 > Stephen --Apple-Mail-CC36B227-A781-455E-846A-8334973818CC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable As I wtote, I would like restrict access to sensitive or= restricted information for some users (eg. hide data of one or more clients= for some database users).

= My question is: do you know some other s= olution to do that ? 
<= span style=3D"caret-color: rgb(0, 0, 0); -webkit-text-size-adjust: auto; bac= kground-color: rgb(255, 255, 255);">
Some 3rd party solution eg= . similar to pgpool or something else ?

= Maybe RLS is th= e beat solution for me. 

T= hank you for your suggestions. 

Wiadomo=C5=9B=C4=87 napisana przez Stephen Frost <sfrost@sno= wman.net> w dniu 08.02.2023, o godz. 01:36:

=EF=BB=BFGreetings,<= /span>

* Joseph Kennedy (joseph.kennedy.486@gmail.= com) wrote:
Thank you Laurenz, I j= ust wanted to make sure.
<= span>
Do you know any= alternative solution to RLS ?

... to do what?  If you want to limit the set of rows that a given use= r

can see, RLS is how to do that.  If you want to limit= the schemas or
tables that a user can see, that isn't possi= ble in PG today (though
there was some interest a while back= in making that work via RLS on the
catalogs which you might= be able to find).

Thanks,
=
Stephen
= --Apple-Mail-CC36B227-A781-455E-846A-8334973818CC--