Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE

Matthew Walden <matthew(dot)walden(dot)list(at)gmail(dot)com> wrote:

> You can create a trigger on the table to store the old/new values in an audit
> table if that is what you mean?

Or he can use tablelog:

16:36 < akretschmer|home> ??tablelog
16:36 < pg_docbot> For information about 'tablelog' see:
16:36 < pg_docbot> http://pgfoundry.org/projects/tablelog/
16:36 < pg_docbot> http://andreas.scherbaum.la/blog/archives/100-Log-Table-Changes-in-PostgreSQL-with-tablelog.html

Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°