diff options
| author | Ben Burwell <ben@benburwell.com> | 2020-04-02 10:40:36 -0400 |
|---|---|---|
| committer | Ben Burwell <ben@benburwell.com> | 2020-04-02 10:40:36 -0400 |
| commit | 7dddde3b6d4a3f95da7fd75bfeae1ed545cbdedb (patch) | |
| tree | 34e3e846be4711ecdc5ae520c29f532382b8c9e2 | |
| parent | 725661fe9d4e996d71843f00fc19b6d664b2aad5 (diff) | |
Reword post from Ethan's feedback
| -rw-r--r-- | _posts/2020-04-02-row-level-security-postgresql-views.md | 2 |
1 files changed, 1 insertions, 1 deletions
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`). |