The usecase in docs mentions: “The goal is to provide the tools needed to produce audit logs required to pass any government, financial, or ISO certification audit.".

I don't care about government, financial or ISO certification audit. What I care is finding queries that touch particular place in system (table). Currently there was no such feature that would let me log queries that touch only specific tables. Of course I could have enabled logging of all queries, but it's not always practical or even possible on production systems.

We know that it was SESSION auditing (more on it later), it was 3rd logged command, and 1st “subcommand" for this command. The level of access was READ, and it was issued by SELECT query. Touched object was a table, and it was pg_catalog.pg_class table. Finally I got information about the query itself.

Query to test2 was not logged because auditor role has access granted only to test. It doesn't mean that I don't have access to test2 table – I have, after all, depesz account is superuser, but logged will be only queries to objects that auditors role has access to.

Or however I will name the role, given that it will be set in pg_audit.role setting.

This is great. I sense a lot of really cool uses for this. There are still rough edges, mostly in docs, like – what is the last column? Should I use pg_audit.log_level, or pg_audit.log_notice?, but in any way – it's a great addition, and I look forward to having it on production DBs. Thanks guys.