Re: pgaudit - an auditing extension for PostgreSQL
От | Abhijit Menon-Sen |
---|---|
Тема | Re: pgaudit - an auditing extension for PostgreSQL |
Дата | |
Msg-id | 20141229120438.GA13085@toroid.org обсуждение исходный текст |
Ответ на | Re: pgaudit - an auditing extension for PostgreSQL (Abhijit Menon-Sen <ams@2ndQuadrant.com>) |
Ответы |
Re: pgaudit - an auditing extension for PostgreSQL
|
Список | pgsql-hackers |
Hi. I've changed pgaudit to work as you suggested. A quick note on the implementation: pgaudit was already installing an ExecutorCheckPerms_hook anyway; I adapted code from ExecRTECheckPerms to check if the audit role has been granted any of the permissions required for the operation. This means there are three ways to configure auditing: 1. GRANT … ON … TO audit, which logs any operations that correspond to the granted permissions. 2. Set pgaudit.roles = 'r1, r2, …', which logs everything done by r1, r2, and any of their descendants. 3. Set pgaudit.log = 'read, write, …', which logs any events in any of the listed classes. (This is a small change from the earlier behaviour where, if a role was listed in .roles, it was still subject to the .log setting. I find that more useful in practice, but since we're discussing Stephen's proposal, I implemented what he said.) The new pgaudit.c is attached here for review. Nothing else has changed from the earlier submission; and everything is in the github repository (github.com/2ndQuadrant/pgaudit). -- Abhijit
Вложения
В списке pgsql-hackers по дате отправления: