Re: Again, sorry, caching. - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Again, sorry, caching.
Date
Msg-id 200204141711.g3EHB2c12445@candle.pha.pa.us
Whole thread Raw
In response to Re: Again, sorry, caching.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Again, sorry, caching.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Also, on the NOTIFY/trigger idea, triggers are called on statement end,
> > not transaction end, so if an UPDATE query is in a multi-statement
> > transaction, another backend looking for the NOTIFY will receive it
> > before the transaction commits, meaning it will not see the update. 
> 
> No it won't.

Is this because NOTIFY is held for transaction end or because the
triggers are held until transaction commit?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Again, sorry, caching.
Next
From: Tom Lane
Date:
Subject: Re: Again, sorry, caching.