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

From Richard Broersma Jr
Subject visibility rules for AFTER UPDATE Constraint Triggers Function
Date
Msg-id 619964.8838.qm@web31805.mail.mud.yahoo.com
Whole thread Raw
Responses Re: visibility rules for AFTER UPDATE Constraint Triggers Function  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I have a PLpgSQL AFTER UPDATE constraint trigger that calls a trigger function with an embedded select statement.

The select statement queries the affected table and returns a mult-result set that includes the record equivalent to
NEW.

However, It seems the select doesn't yet see the non-committed records. I.E. the record that should be equal to NEW is
infact equal to OLD. 

Is this correct? Is there a way to adjust the visibility so that yet-to-be committed tuples are seen by the trigger
function?

Regards,
Richard Broersma Jr.



pgsql-general by date:

Previous
From: Greg Smith
Date:
Subject: Re: basic questions: Postgres with yum on CentOS 5.1
Next
From: Tom Lane
Date:
Subject: Re: visibility rules for AFTER UPDATE Constraint Triggers Function