Re: Proposal: SET ROLE hook - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Proposal: SET ROLE hook
Date
Msg-id CAFj8pRAx3AnSeF0CWRMLFejgbBG2Z-Nw85zdCDamoSdZqeBgYg@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: SET ROLE hook  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers


Ultimately I would also like to see a general hook available which would
fire for all changes to GUC settings, but I think this one is still very
useful as it is highly targeted.

Comments?

I read discussion in this thread and I am thinking so creating hook is the most simple and workable solution.

Personally, I am not sure if missing support SECURE DEFINER function is ok. When you do some secure audit, probably any role change can be interesting. This situation can be distinguished by another hook parameter.

I though more about this topic, and my request was +/- premature optimization. It can be solved simply in future by different hook when it be requested. This should not be blocker.

Regards

Pavel
 

Support of event triggers can be other topic, nice to have it but not necessary in first moment.

Regards

Pavel
 

Thanks,

Joe

--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development



pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: COPY (... tab completion
Next
From: Amit Langote
Date:
Subject: Re: Regression caused by recent change to initdb?