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

2010-11-17 Thread Andreas Kretschmer
Matthew Walden 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/p

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

2010-11-17 Thread Matthew Walden
You can create a trigger on the table to store the old/new values in an audit table if that is what you mean?

[GENERAL] Storing old and new tuple values after an UPDATE, INSERT or DELETE

2010-11-17 Thread rmd22
Is it possible to modify source code in executor to keep a log of old tuples and new tuples after an UPDATE, INSERT or DELETE command is executed? (so basically Store Old Tuple Values -> UPDATE/INSERT/DELETE Command -> Store New Tuple Values) For example is it possible to modify the execMain.c fi