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 108138.94307.qm@web31808.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>)
List pgsql-general
--- On Wed, 1/2/08, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> [ pokes at it... ]  The reason is that you defined both the trigger and
> the testing function as STABLE, which means that they see a snapshot of
> the database as of the start of the calling SQL command.  In the first
> case that's the UPDATE, in the second it's the COMMIT.

Thanks for the help Tom.  This information is good to know.

Regards,
Richard Broersma Jr.

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: [SQL] PG is in different timezone than the OS
Next
From: Martin Langhoff
Date:
Subject: PITR - filter by database?