From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | stan <stanb(at)panix(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Detecting which columns a query will modify in a function called by a trigger |
Date: | 2020-03-02 19:02:54 |
Message-ID: | 30c3c06e-61fa-3210-666d-1696af320a75@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
On 3/2/20 10:59 AM, stan wrote:
> I need to implement a fairly fine grained security model. Probably a bit
> finer that I can do with the standard ownership functionality.
>
> My thinking on this is to create a table that contains the users, and a
> "permission bit" for each function that they may want to do, vis a vi
> altering an existing row,or rows, or inserting new rows.
>
> Looks relatively straight forward, if fairly time consuming to do. But I
> would need to know which column(s) a given query would add..alter from the
> function to implement this via a trigger. looks like I see most of what I
> need t do this in the docs, but I can't quite figure out if I can get this
> down to what column(s) a given trigger will modify. Is this possible?
Before you get too far into this I would look at RLS:
https://www.postgresql.org/docs/12/ddl-rowsecurity.html
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2020-03-02 19:04:02 | Re: Detecting which columns a query will modify in a function called by a trigger |
Previous Message | stan | 2020-03-02 18:59:04 | Detecting which columns a query will modify in a function called by a trigger |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2020-03-02 19:04:02 | Re: Detecting which columns a query will modify in a function called by a trigger |
Previous Message | stan | 2020-03-02 18:59:04 | Detecting which columns a query will modify in a function called by a trigger |