On 10/08/2018 21:20, dangal wrote:
Achilleas thanks for your answer
A query, the only possible way out is the postgres log?
I would like to be able to throw the audit output to a different place so
that I can not access the file
Yes, only the postgresql log, and you gotta take care of ^M (CR), C
Achilleas thanks for your answer
A query, the only possible way out is the postgres log?
I would like to be able to throw the audit output to a different place so
that I can not access the file
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
On 10/08/2018 17:01, dangal wrote:
Dear, I would like to ask you to see what you recommend
I manage a production database with a nominated user with the same
permissions as the postgres user SUPERUSER INHERIT CREATEDB CREATEROLE
REPLICATION
The client is asking us for an audit about this nominate
Dear, I would like to ask you to see what you recommend
I manage a production database with a nominated user with the same
permissions as the postgres user SUPERUSER INHERIT CREATEDB CREATEROLE
REPLICATION
The client is asking us for an audit about this nominated user, could you
recommend any ext
