Re: Auditing extension for PostgreSQL (Take 2) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Auditing extension for PostgreSQL (Take 2)
Date
Msg-id 554BCE32.7010709@gmx.net
Whole thread Raw
In response to Re: Auditing extension for PostgreSQL (Take 2)  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Auditing extension for PostgreSQL (Take 2)  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 5/7/15 10:26 AM, Stephen Frost wrote:
> Auditing is about "what happened" whereas
> statement logging is "log whatever statement the user sent."  pgAudit
> bears this out by logging internal SQL statements and object
> information, unlike what we do with statement logging today.

I don't think this is quite correct.  For example,
log_min_duration_statement logs based on what happened.  log_duration
records what happened.  log_checkpoints records what happened.
log_statement also requires parsing before deciding whether to log.

Generally, "logging" is "what happened".  The stuff in syslog is what
happened on the system.




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Fixing busted citext function declarations
Next
From: Robert Haas
Date:
Subject: Re: Disabling trust/ident authentication configure option