Re: Audit trail

I'd recommend using rules to improve your efficiency for queries affect more
than one row..

Josh.

On March 13, 2003 09:33 am, James Gregory wrote:
> Hi all,
>
> I am wondering if anyone has any good solutions for having postgres
> leave an audit trail. Specifically I would like it to copy rows to a
> ghost table without constraints every time a row is modified, deleted
> etc. I don't really want to have to do the work of creating said ghost
> tables, but if that's the only way, then that's ok.
>
> I know about Audit Trail, and it seems ok, but it's not suitable here
> because:
>
> 1. It doesn't copy whole rows
> 2. It requires that your tables adhere to a particular structure (I'm
> new in this company and I'm slowly migrating tables to a structure that
> is close enough that it could be made to work, but for now I'm stuck
> with what's here)
>
> Is it best to write some triggers or has someone already done this
> stuff?
>
> Thanks,
>
> James.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly