From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
---|---|
To: | Murray Prior Hobbs <murray(at)efone(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Auditing and Postgres 7.3 |
Date: | 2002-01-23 13:01:21 |
Message-ID: | Pine.LNX.4.21.0201232359130.15773-100000@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Murray,
On Wed, 23 Jan 2002, Murray Prior Hobbs wrote:
> in fact. if i was to want to design a database system for "commercial"
> use the very first thing i would start with would be the audit system
>
> objects oriented? no, after audit
>
> referenential integrety?, no, after audit
>
> really - even just on a practicality basis the audit is essential
>
> there needs to be a front end to the database - a completely new layer -
> that layer feeds the database and no other and that layer is itself the
> audit trail
>
> it should be possible to run an audit trail backwards against a database
> and undo everything back to an earlier state (assuming that this is done
> in standalone mode)
You seem to be confusing my defition of audit (track user queries, not
the effect they have on the database) with 'transaction logging' or
'journalling'. The latter is the job of the write-ahead log already
implemented in Postgres.
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2002-01-23 13:09:41 | Re: Auditing and Postgres 7.3 |
Previous Message | Murray Prior Hobbs | 2002-01-23 12:56:47 | Re: Auditing and Postgres 7.3 |