From: | Holger Jakobs <holger(at)jakobs(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org, "Burhan Akbulut (ETIYA)" <burhan(dot)akbulut(at)etiya(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Restrict user's query row number |
Date: | 2021-08-26 14:27:42 |
Message-ID: | D320C759-4075-43D1-AE65-17191A94EB02@jakobs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Am 26. August 2021 14:05:34 MESZ schrieb "Burhan Akbulut (ETIYA)" <burhan(dot)akbulut(at)etiya(dot)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(dot)akbulut(at)etiya(dot)com<mailto:burhan(dot)akbulut(at)etiya(dot)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 -
From | Date | Subject | |
---|---|---|---|
Next Message | Pepe TD Vo | 2021-08-26 21:09:20 | slave stops replica |
Previous Message | Laurenz Albe | 2021-08-26 13:23:15 | Re: Restrict user's query row number |