{"id":8813,"date":"2016-09-02T08:11:47","date_gmt":"2016-09-02T06:11:47","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/"},"modified":"2023-06-08T15:19:51","modified_gmt":"2023-06-08T13:19:51","slug":"understanding-row-level-security-on-postgresql","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/","title":{"rendered":"Understanding Row Level Security on PostgreSQL"},"content":{"rendered":"

By Mouhamadou Diaw<\/strong><\/p>\n

In this article we will talk about a nice feature Row Level Security on PostgreSQL. We are using <\/span>EDB Postgres<\/span><\/b><\/em>\u00a0<\/span><\/span>Advanced Server\u00a0<\/span><\/span>9.5<\/span><\/b><\/em>.
\n<\/span>Suppose that I am a team manager and that employee bonus are stored in a table Bonus. I want that each employee can see only data related to him and not data for other. How Can I implement this?\u00a0I can simply use Row Level Security<\/span>.
\nLet\u2019s go on. Below is the structure of my table Bonus<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n<\/td>\n
\n
\n
testdb=# d Bonus<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Table<\/code> \"public.bonus\"<\/code><\/div>\n
\u00a0<\/code>Column<\/code> |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Type\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | Modifiers<\/code><\/div>\n
--------+-----------------------+-----------<\/code><\/div>\n
\u00a0<\/code>id\u00a0\u00a0\u00a0\u00a0 | <\/code>numeric<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | <\/code>not<\/code> null<\/code><\/div>\n
\u00a0<\/code>login\u00a0\u00a0 | <\/code>character<\/code> varying<\/code>(20) |<\/code><\/div>\n
\u00a0<\/code>bonus\u00a0 | <\/code>numeric<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
Indexes:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0<\/code>\"bonus_pkey\"<\/code> PRIMARY<\/code> KEY<\/code>, btree (id)<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Below data inside Bonus<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n<\/td>\n
\n
\n
testdb=# <\/code>table<\/code> bonus;<\/code><\/div>\n
\u00a0<\/code>id |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 login\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | bonus<\/code><\/div>\n
----+----------------------+-------<\/code><\/div>\n
\u00a0\u00a0<\/code>1 | james@example.com\u00a0\u00a0\u00a0 |\u00a0 2500<\/code><\/div>\n
\u00a0\u00a0<\/code>2 | Moise@example.com\u00a0\u00a0\u00a0 |\u00a0 1500<\/code><\/div>\n
\u00a0\u00a0<\/code>3 | Mikael@example.com\u00a0\u00a0 |\u00a0 7500<\/code><\/div>\n
\u00a0\u00a0<\/code>4 | jennifer@example.com |\u00a0 3520<\/code><\/div>\n
(4 <\/code>rows<\/code>)<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Let\u2019s create users with corresponding logins<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n<\/td>\n
\n
\n
testdb=# <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0<\/code>current_user<\/code><\/div>\n
--------------<\/code><\/div>\n
\u00a0<\/code>enterprisedb<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=# <\/code>create<\/code> user<\/code> \"james@example.com\"<\/code> password<\/code> 'secret'<\/code>;<\/code><\/div>\n
CREATE<\/code> ROLE<\/code><\/div>\n
testdb=# <\/code>create<\/code> user<\/code> \"Moise@example.com\"<\/code> password<\/code> 'secret'<\/code>;<\/code><\/div>\n
CREATE<\/code> ROLE<\/code><\/div>\n
testdb=# <\/code>create<\/code> user<\/code> \"jennifer@example.com\"<\/code> password<\/code> 'secret'<\/code>;<\/code><\/div>\n
CREATE<\/code> ROLE<\/code><\/div>\n
testdb=# <\/code>create<\/code> user<\/code> \"Mikael@example.com\"<\/code> password<\/code> 'secret'<\/code>;<\/code><\/div>\n
CREATE<\/code> ROLE<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And let\u2019s grant them select on Table Bonus<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n<\/td>\n
\n
\n
testdb=# <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0<\/code>current_user<\/code><\/div>\n
--------------<\/code><\/div>\n
\u00a0<\/code>enterprisedb<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=# <\/code>grant<\/code> select<\/code> on<\/code> bonus <\/code>to<\/code> \"james@example.com\"<\/code>;<\/code><\/div>\n
GRANT<\/code><\/div>\n
testdb=# <\/code>grant<\/code> select<\/code> on<\/code> bonus <\/code>to<\/code> \"Moise@example.com\"<\/code>;<\/code><\/div>\n
GRANT<\/code><\/div>\n
testdb=# <\/code>grant<\/code> select<\/code> on<\/code> bonus <\/code>to<\/code> \"Mikael@example.com\"<\/code>;<\/code><\/div>\n
GRANT<\/code><\/div>\n
testdb=# <\/code>grant<\/code> select<\/code> on<\/code> bonus <\/code>to<\/code> \"jennifer@example.com\"<\/code>;<\/code><\/div>\n
GRANT<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

We can verify that \u00a0by default <\/span> \u00a0 each user can see all data (what I don\u2019t want<\/span>).\u00a0<\/span>For example with user james@example.com<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n<\/td>\n
\n
\n
testdb=> <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0\u00a0\u00a0<\/code>current_user<\/code><\/div>\n
-------------------<\/code><\/div>\n
\u00a0<\/code>james@example.com<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=> <\/code>select<\/code> * <\/code>from<\/code> bonus;<\/code><\/div>\n
\u00a0<\/code>id |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 login\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | bonus<\/code><\/div>\n
----+----------------------+-------<\/code><\/div>\n
\u00a0\u00a0<\/code>1 | james@example.com\u00a0\u00a0\u00a0 |\u00a0 2500<\/code><\/div>\n
\u00a0\u00a0<\/code>2 | Moise@example.com\u00a0\u00a0\u00a0 |\u00a0 1500<\/code><\/div>\n
\u00a0\u00a0<\/code>3 | Mikael@example.com\u00a0\u00a0 |\u00a0 7500<\/code><\/div>\n
\u00a0\u00a0<\/code>4 | jennifer@example.com |\u00a0 3520<\/code><\/div>\n
(4 <\/code>rows<\/code>)<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And with user jennifer@example.com<\/span><\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n<\/td>\n
\n
\n
testdb=> <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>current_user<\/code><\/div>\n
----------------------<\/code><\/div>\n
\u00a0<\/code>jennifer@example.com<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=> <\/code>select<\/code> * <\/code>from<\/code> bonus;<\/code><\/div>\n
\u00a0<\/code>id |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 login\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | bonus<\/code><\/div>\n
----+----------------------+-------<\/code><\/div>\n
\u00a0\u00a0<\/code>1 | james@example.com\u00a0\u00a0\u00a0 |\u00a0 2500<\/code><\/div>\n
\u00a0\u00a0<\/code>2 | Moise@example.com\u00a0\u00a0\u00a0 |\u00a0 1500<\/code><\/div>\n
\u00a0\u00a0<\/code>3 | Mikael@example.com\u00a0\u00a0 |\u00a0 7500<\/code><\/div>\n
\u00a0\u00a0<\/code>4 | jennifer@example.com |\u00a0 3520<\/code><\/div>\n
(4 <\/code>rows<\/code>)<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

To allow user to see only his data. I have first to create a policy <\/span> on the table Bonus with an expression which will filter data.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n<\/td>\n
\n
\n
testdb=# <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0<\/code>current_user<\/code><\/div>\n
--------------<\/code><\/div>\n
\u00a0<\/code>enterprisedb<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=# <\/code>create<\/code> policy bonus_policy <\/code>on<\/code> bonus <\/code>for<\/code> all<\/code> to<\/code> public<\/code> using (login=<\/code>current_user<\/code>);<\/code><\/div>\n
CREATE<\/code> POLICY<\/code><\/div>\n
testdb=#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

After creating the policy, let’s enable the RLS on table Bonus<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n<\/td>\n
\n
\n
testdb=# <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0<\/code>current_user<\/code><\/div>\n
--------------<\/code><\/div>\n
\u00a0<\/code>enterprisedb<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=# <\/code>alter<\/code> table<\/code> bonus enable row <\/code>level<\/code> security;<\/code><\/div>\n
ALTER<\/code> TABLE<\/code><\/div>\n
testdb=#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And now bingo we can \u00a0verify that each user can only see his corresponding data<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n<\/td>\n
\n
\n
testdb=> <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>current_user<\/code><\/div>\n
----------------------<\/code><\/div>\n
\u00a0<\/code>jennifer@example.com<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=> <\/code>select<\/code> * <\/code>from<\/code> bonus;<\/code><\/div>\n
\u00a0<\/code>id |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 login\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | bonus<\/code><\/div>\n
----+----------------------+-------<\/code><\/div>\n
\u00a0\u00a0<\/code>4 | jennifer@example.com |\u00a0 3520<\/code><\/div>\n
(1 row)<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n
\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n<\/td>\n
\n
\n
testdb=> <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0\u00a0\u00a0<\/code>current_user<\/code><\/div>\n
-------------------<\/code><\/div>\n
\u00a0<\/code>james@example.com<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=> <\/code>select<\/code> * <\/code>from<\/code> bonus;<\/code><\/div>\n
\u00a0<\/code>id |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 login\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | bonus<\/code><\/div>\n
----+-------------------+-------<\/code><\/div>\n
\u00a0\u00a0<\/code>1 | james@example.com |\u00a0 2500<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Now let\u2019s drop the policy but let\u2019s still keep table bonus with the RLS enabled. What happens? <\/span><\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n<\/td>\n
\n
\n
testdb=# <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0<\/code>current_user<\/code><\/div>\n
--------------<\/code><\/div>\n
\u00a0<\/code>enterprisedb<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=# <\/code>drop<\/code> policy bonus_policy <\/code>on<\/code> bonus;<\/code><\/div>\n
DROP<\/code> POLICY<\/code><\/div>\n
testdb=#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Let\u2019s Query \u00a0table bonus with user james@example.com for example<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n<\/td>\n
\n
\n
testdb=> <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0\u00a0\u00a0<\/code>current_user<\/code><\/div>\n
-------------------<\/code><\/div>\n
\u00a0<\/code>james@example.com<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=> <\/code>select<\/code> * <\/code>from<\/code> bonus;<\/code><\/div>\n
\u00a0<\/code>id | login | bonus<\/code><\/div>\n
----+-------+-------<\/code><\/div>\n
(0 <\/code>rows<\/code>)<\/code><\/div>\n
<\/div>\n
testdb=><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

But if we query the table with user enterprisedb which is the table owner (should also be a superuser)<\/span><\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n<\/td>\n
\n
\n
testdb=# <\/code>select<\/code> current_user<\/code>;<\/code><\/div>\n
\u00a0<\/code>current_user<\/code><\/div>\n
--------------<\/code><\/div>\n
\u00a0<\/code>enterprisedb<\/code><\/div>\n
(1 row)<\/code><\/div>\n
<\/div>\n
testdb=# <\/code>select<\/code> * <\/code>from<\/code> bonus;<\/code><\/div>\n
\u00a0<\/code>id |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 login\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | bonus<\/code><\/div>\n
----+----------------------+-------<\/code><\/div>\n
\u00a0\u00a0<\/code>1 | james@example.com\u00a0\u00a0\u00a0 |\u00a0 2500<\/code><\/div>\n
\u00a0\u00a0<\/code>2 | Moise@example.com\u00a0\u00a0\u00a0 |\u00a0 1500<\/code><\/div>\n
\u00a0\u00a0<\/code>3 | Mikael@example.com\u00a0\u00a0 |\u00a0 7500<\/code><\/div>\n
\u00a0\u00a0<\/code>4 | jennifer@example.com |\u00a0 3520<\/code><\/div>\n
(4 <\/code>rows<\/code>)<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

So we see that if RLS is enabled on a table and that there is no defined policy, a default-deny\u00a0 policy will be applied. Only owners, super users and users \u00a0with the BYPASSRLS attribute will be able to see data in the table<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw In this article we will talk about a nice feature Row Level Security on PostgreSQL. We are using EDB Postgres\u00a0Advanced Server\u00a09.5. Suppose that I am a team manager and that employee bonus are stored in a table Bonus. I want that each employee can see only data related to him and not […]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[77],"type_dbi":[],"class_list":["post-8813","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-postgresql"],"acf":[],"yoast_head":"\nUnderstanding Row Level Security on PostgreSQL - dbi Blog<\/title>\n<meta name=\"description\" content=\"Row level Policy , Row Level Security, PostgreSQL Security, Open source\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Understanding Row Level Security on PostgreSQL\" \/>\n<meta property=\"og:description\" content=\"Row level Policy , Row Level Security, PostgreSQL Security, Open source\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-09-02T06:11:47+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-08T13:19:51+00:00\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Understanding Row Level Security on PostgreSQL\",\"datePublished\":\"2016-09-02T06:11:47+00:00\",\"dateModified\":\"2023-06-08T13:19:51+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/\"},\"wordCount\":285,\"commentCount\":0,\"keywords\":[\"PostgreSQL\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/\",\"name\":\"Understanding Row Level Security on PostgreSQL - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2016-09-02T06:11:47+00:00\",\"dateModified\":\"2023-06-08T13:19:51+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"Row level Policy , Row Level Security, PostgreSQL Security, Open source\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Understanding Row Level Security on PostgreSQL\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Understanding Row Level Security on PostgreSQL - dbi Blog","description":"Row level Policy , Row Level Security, PostgreSQL Security, Open source","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/","og_locale":"en_US","og_type":"article","og_title":"Understanding Row Level Security on PostgreSQL","og_description":"Row level Policy , Row Level Security, PostgreSQL Security, Open source","og_url":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/","og_site_name":"dbi Blog","article_published_time":"2016-09-02T06:11:47+00:00","article_modified_time":"2023-06-08T13:19:51+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Understanding Row Level Security on PostgreSQL","datePublished":"2016-09-02T06:11:47+00:00","dateModified":"2023-06-08T13:19:51+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/"},"wordCount":285,"commentCount":0,"keywords":["PostgreSQL"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/","url":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/","name":"Understanding Row Level Security on PostgreSQL - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2016-09-02T06:11:47+00:00","dateModified":"2023-06-08T13:19:51+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"Row level Policy , Row Level Security, PostgreSQL Security, Open source","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/understanding-row-level-security-on-postgresql\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Understanding Row Level Security on PostgreSQL"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8813","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=8813"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8813\/revisions"}],"predecessor-version":[{"id":25678,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8813\/revisions\/25678"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=8813"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=8813"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=8813"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=8813"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}