pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org, "Burhan Akbulut (ETIYA)" <burhan.akbulut@etiya.com>
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Restrict user's query row number
Date: Thu, 26 Aug 2021 16:27:42 +0200
Message-ID: <D320C759-4075-43D1-AE65-17191A94EB02@jakobs.com> (raw)
In-Reply-To: <VI1PR01MB703983265286DE36A7FE7AB589C79@VI1PR01MB7039.eurprd01.prod.exchangelabs.com>
References: <VI1PR01MB703983265286DE36A7FE7AB589C79@VI1PR01MB7039.eurprd01.prod.exchangelabs.com>



Am 26. August 2021 14:05:34 MESZ schrieb "Burhan Akbulut (ETIYA)" <burhan.akbulut@etiya.com>:
>Hello,
>
>Some tables that contain sensitive data can be accessed by many people from the operation team. I want to limit rows the results of queries containing these tables through client applications such as Pgadmin or DBeaver.
>
>Can I do this exactly? How can I do it if I can?
>
>PS: The operations team does not use similar queries. I can solve this problem with using view or etc, if they are using the same queries. However, they produce new types of queries by combining different tables and tables containing sensitive data.
>
>Thanks for your help.
>
>Burhan Akbulut
>Etiya
>
>[https://www.etiya.com/images/e-newsletter/signature/etiya_logo.png]
>[http://www.etiya.com/images/e-newsletter/signature/e_adres.png]<http://www.etiya.com;
>[http://www.etiya.com/images/e-newsletter/signature/facebook_icon.png]<https://www.facebook.com/Etiya-249050755136326/; [http://www.etiya.com/images/e-newsletter/signature/linkedin_icon.png] <https://www.linkedin.com/company/etiya?trk=tyah&trkInfo=tas%3Aetiya%2Cidx%3A1-1-1;  [http://www.etiya.com/images/e-newsletter/signature/instagram_icon.png] <https://www.instagram.com/etiya_/;  [http://www.etiya.com/images/e-newsletter/signature/youtube_icon.png] <https://www.youtube.com/channel/UCWjknu72sHoKKt2nujuU2kA;  [http://www.etiya.com/images/e-newsletter/signature/twitter_icon.png] <https://twitter.com/etiya;
>[http://www.etiya.com/images/e-newsletter/signature/0.png]
>
>Burhan Akbulut
>Senior Specialist, Database Management
>
>
>M:+90 552 997 52 97
>E:burhan.akbulut@etiya.com<mailto:burhan.akbulut@etiya.com>
>
>
>
>
>
>Yasal Uyari :
>Bu elektronik posta asagidaki adreste bulunan Kosul ve Sartlara tabidir;
>http://www.etiya.com/gizlilik<www.etiya.com/gizlilik;
>
>?IKTI ALMADAN ?NCE ?EVREYE OLAN SORUMLULUGUMUZU BIR KEZ DAHA D?S?NELIM.
>PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING ANY DOCUMENT.


Do you want to limit according to some criterion or the number of rows which may be returned?

The first would be row level security.

The second would be a view with a 'limit' clause.


-- 
Holger Jakobs, Bergisch Gladbach
+49 178 9759012
- sent from mobile, therefore short -

view thread (4+ messages)

Message-ID: <D320C759-4075-43D1-AE65-17191A94EB02@jakobs.com>
Permalink:  ../D320C759-4075-43D1-AE65-17191A94EB02@jakobs.com/
Also on:    postgresql.org/message-id/D320C759-4075-43D1-AE65-17191A94EB02@jakobs.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: holger@jakobs.com, burhan.akbulut@etiya.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Restrict user's query row number
  In-Reply-To: <D320C759-4075-43D1-AE65-17191A94EB02@jakobs.com>

* 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