From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: SET ROLE hook |
Date: | 2016-01-06 09:24:01 |
Message-ID: | CAFj8pRAx3AnSeF0CWRMLFejgbBG2Z-Nw85zdCDamoSdZqeBgYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
>>
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2016-01-06 09:57:32 | Re: Regression caused by recent change to initdb? |
Previous Message | Andreas Karlsson | 2016-01-06 09:20:13 | Re: COPY (... tab completion |