From 7dddde3b6d4a3f95da7fd75bfeae1ed545cbdedb Mon Sep 17 00:00:00 2001 From: Ben Burwell Date: Thu, 2 Apr 2020 10:40:36 -0400 Subject: Reword post from Ethan's feedback --- _posts/2020-04-02-row-level-security-postgresql-views.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2020-04-02-row-level-security-postgresql-views.md b/_posts/2020-04-02-row-level-security-postgresql-views.md index 223cf88..7430215 100644 --- a/_posts/2020-04-02-row-level-security-postgresql-views.md +++ b/_posts/2020-04-02-row-level-security-postgresql-views.md @@ -134,7 +134,7 @@ the `postgres` superuser) rather than the current user. How can we fix this? Changing the owner of the view wouldn't help us because then all the customer users would just see `customer_a`'s data. -One solution would be to create a function that does the selection. In Postgres, +My solution was to create a function that does the selection. In Postgres, functions can either be run with the privileges of the user who created them (by specifying `SECURITY DEFINER`), or as the user calling them (with `SECURITY INVOKER`). -- cgit v1.2.3