Re: visibility rules for AFTER UPDATE Constraint Triggers Function

From: Richard Broersma Jr <rabroersma(at)yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: General PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: visibility rules for AFTER UPDATE Constraint Triggers Function
Date: 2008-01-02 20:48:39
Message-ID: 108138.94307.qm@web31808.mail.mud.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

--- On Wed, 1/2/08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joe 2008-01-02 20:49:24 Re: Argentinian timezone change at the last moment. How to change pgsql tz db?
Previous Message Scott Marlowe 2008-01-02 20:31:24 Re: [SQL] PG is in different timezone than the OS