Postgres Pro
Downloads
Home   >   mailing lists

Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE - Mailing list pgsql-general

From Matthew Walden
Subject Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Date
Msg-id AANLkTim73HhK+8UEbwUDdgg987UhMXsbHAk6ThFw2YZU@mail.gmail.com
Whole thread Raw
In response to Storing old and new tuple values after an UPDATE, INSERT or DELETE  (rmd22 <rohit.dhamane@gmail.com>)
Responses Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE  (Andreas Kretschmer <akretschmer@spamfence.net>)
Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE  (rmd22 <rohit.dhamane@gmail.com>)
List pgsql-general
Tree view
You can create a trigger on the table to store the old/new values in an audit table if that is what you mean?

pgsql-general by date:

Previous
From: rmd22
Date:
Subject: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Next
From: Matthew Walden
Date:
Subject: Re: interactive pager off