Re: Re: Modfying source code to read tuples before and after UPDATE...how to? - Mailing list pgsql-general

From John R Pierce
Subject Re: Re: Modfying source code to read tuples before and after UPDATE...how to?
Date
Msg-id 4CD58F9E.30304@hogranch.com
Whole thread Raw
In response to Re: Modfying source code to read tuples before and after UPDATE...how to?  (rmd22 <rohit.dhamane@gmail.com>)
List pgsql-general
On 11/05/10 9:23 AM, rmd22 wrote:
> Well what i mean by print out is that it should print out the old and new
> tuples on postgres terminal after the update is complete.
> I tried it with triggers and I got what I wanted. But my professor for some
> reason wants me to mess around with the source code :(
> Do you think it's possible?

what is the 'postgres terminal'  ?  its a service, running as a daemon,
it has no console normally, just a logfile.


should that only be printing tuples that are committed?   that becomes a
LOT harder.

a single UPDATE statement can modify a huge number of tuples.   also
ALTER TABLE statements can modify tuples, and of course INSERT
statements create new tuples.



pgsql-general by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Thoughts on a surrogate key lookup function?
Next
From: Nick
Date:
Subject: Re: Thoughts on a surrogate key lookup function?