[HACKERS] pg audit requirements

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема [HACKERS] pg audit requirements
Дата
Msg-id CAFj8pRDhRDpsZTsp7HxsBi2jh16oZXhouUA6i5qCnsnLFbXtAw@mail.gmail.com
обсуждение исходный текст
Ответы Re: [HACKERS] pg audit requirements
Список pgsql-hackers
Hi

I am sending some notes, experience about usage of pgAudit.

pgAudit provides basic functionality and usually is good enough. But it is not good enough for some applications in financial services.

The requirements:

1. structured output - attached query is not good enough - column name, table name, schema, database, role should be separated

2. separated log (log file) with guaranteed write - fsync after every line means significant performance issue, but fsync every 1sec (or defined interval) is acceptable

3. security issues - not enough access rights to database object should be processed and logged in audit log too.

Regards

Pavel

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: Re: [HACKERS] proposal: psql command \graw
Следующее
От: David Rowley
Дата:
Сообщение: Re: [HACKERS] path toward faster partition pruning