| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| 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:09:41 |
| Message-ID: | 200201231309.IAA17065@www.wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday 23 January 2002 07:56 am, Murray Prior Hobbs wrote:
> the lack of a true full audit trail capabiity in postgres is perhaps
> it's biggest fundamental weakness as a "commercial" use system
> 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
Understand that Postgres was *never* designed to be a 'commercial' use system
from the ground up. It was originally designed as a research platform. We
are hammering at it becoming commercial-grade, though.
Gavin's idea sounds OK to me -- although you can get that information now
from the query logs if you set the logging up. It's not per-table --- and I
like the per-table idea. This audit trail would make a handy debugging log
as well.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2002-01-23 13:13:02 | Re: Auditing and Postgres 7.3 |
| Previous Message | Gavin Sherry | 2002-01-23 13:01:21 | Re: Auditing and Postgres 7.3 |