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

From rmd22
Subject Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Date
Msg-id 1290008229144-3269213.post@n5.nabble.com
Whole thread Raw
In response to Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE  (Matthew Walden <matthew.walden.list@gmail.com>)
Responses Re: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE  (David Fetter <david@fetter.org>)
List pgsql-general
Yes I have tried it with triggers but I have to do it without using triggers.
Since in my workplace someone has already done that and for some reason (may
be because triggers are expensive i suppose...not sure though), hence they
want me to do it by modifying the source code.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Storing-old-and-new-tuple-values-after-an-UPDATE-INSERT-or-DELETE-tp3269108p3269213.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

pgsql-general by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: The first dedicated PostgreSQL forum
Next
From: Tom Lane
Date:
Subject: Re: Survey on backing up unlogged tables: help us with PostgreSQL development!