Re: Problem with async notifications of table updates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tyler, Mark" <Mark(dot)Tyler(at)dsto(dot)defence(dot)gov(dot)au>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with async notifications of table updates
Date: 2008-03-18 02:35:24
Message-ID: 7251.1205807724@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Tyler, Mark" <Mark(dot)Tyler(at)dsto(dot)defence(dot)gov(dot)au> writes:
> What I want to do is to guarantee that the row is available for
> selection prior to sending the message.

You cannot do that with an AFTER trigger, because whatever it does
necessarily happens before your transaction commits. I suggest
rethinking your dislike of NOTIFY.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tyler, Mark 2008-03-18 02:58:36 Re: Problem with async notifications of table updates
Previous Message Adam Rich 2008-03-18 02:26:36 Re: 8.3.0 upgrade