visibility rules for AFTER UPDATE Constraint Triggers Function

From: Richard Broersma Jr <rabroersma(at)yahoo(dot)com>
To: General PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: visibility rules for AFTER UPDATE Constraint Triggers Function
Date: 2008-01-02 05:25:12
Message-ID: 619964.8838.qm@web31805.mail.mud.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 in fact 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.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-01-02 05:35:57 Re: basic questions: Postgres with yum on CentOS 5.1
Previous Message Greg Smith 2008-01-02 04:59:44 Re: basic questions: Postgres with yum on CentOS 5.1