Re: visibility rules for AFTER UPDATE Constraint Triggers Function - Mailing list pgsql-general

From Richard Broersma Jr
Subject Re: visibility rules for AFTER UPDATE Constraint Triggers Function
Date
Msg-id 914600.47286.qm@web31807.mail.mud.yahoo.com
Whole thread Raw
In response to Re: visibility rules for AFTER UPDATE Constraint Triggers Function  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: visibility rules for AFTER UPDATE Constraint Triggers Function
List pgsql-general
--- On Tue, 1/1/08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Please provide a self-contained example.

Basically the example demonstrates the difference a single tuple UPDATE when preformed the following two ways:

UPDATE table ...;  -- Sees OLD.

BEGIN; UPDATE table ...; COMMIT; --Sees NEW.

I was my understanding that all single DML statement are wrapped in their own transaction so I thought that these two
statementsshould preform the same. 

Regards,
Richard Broersma Jr.

Attachment

pgsql-general by date:

Previous
From: "Pavel Stehule"
Date:
Subject: Re: group by and count(*) behaviour in 8.3
Next
From: Glyn Astill
Date:
Subject: Fwd: [ADMIN] Shutting down warm standby server? "