| From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "'Murray Prior Hobbs'" <murray(at)efone(dot)com>, Justin Clift <justin(at)postgresql(dot)org> |
| Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Auditing and Postgres 7.3 |
| Date: | 2002-01-23 13:13:02 |
| Message-ID: | FED2B709E3270E4B903EB0175A49BCB1047474@dogbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: Murray Prior Hobbs [mailto:murray(at)efone(dot)com]
> Sent: 23 January 2002 12:57
> To: Justin Clift
> Cc: Gavin Sherry; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Auditing and Postgres 7.3
>
> 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)
>
> the audit then IS the database - or rather it IS the data -
> all of it -
> and ideally it wold be in a form that is almost human readable
>
I may be way off (often am in fact :-) ), but isn't this basically the time
travel that I believe was removed in 6.3?
/Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Michel POURE | 2002-01-23 13:44:17 | Add OR REPLACE clauses to non-FUNCTION object creation in PostgreSQL 7.3 |
| Previous Message | Lamar Owen | 2002-01-23 13:09:41 | Re: Auditing and Postgres 7.3 |