Re: Inserts restricted to a trigger

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Miles Elam <miles(dot)elam(at)productops(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Inserts restricted to a trigger
Date: 2019-06-20 15:01:09
Message-ID: 48ddb8b0-2628-9b9e-84c4-955f5c15ddd1@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 6/19/19 3:07 PM, Miles Elam wrote:
> Hi Adrian, thanks for responding.
>
> How would I restrict access to the SECURITY DEFINER function? If it can
> be called by the trigger, it can be called by the user as well I would
> think. Same issue as access to the table itself only now with a
> superuser intermediary, right?
>

Should have also mentioned, if you are not adverse to a third party
solution there is PGAudit:

https://www.pgaudit.org/

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Shay Rojansky 2019-06-20 15:22:20 Re: Row data is reflected in DETAIL message when constraints fail on insert/update
Previous Message Tom Lane 2019-06-20 14:55:35 Re: [EXT EMAIL] Re: First Time Starting Up PostgreSQL and Having Problems