Re: Re: Modfying source code to read tuples before and after UPDATE...how to?

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Re: Modfying source code to read tuples before and after UPDATE...how to?
Date: 2010-11-06 17:25:50
Message-ID: 4CD58F9E.30304@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jasen Betts 2010-11-06 21:29:38 Re: avoiding nested loops when joining on partitioned tables
Previous Message Nick 2010-11-06 17:01:22 Re: Thoughts on a surrogate key lookup function?