| From: | Klint Gore <kgore4(at)une(dot)edu(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Tyler, Mark" <Mark(dot)Tyler(at)dsto(dot)defence(dot)gov(dot)au>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problem with async notifications of table updates |
| Date: | 2008-03-19 23:06:11 |
| Message-ID: | 47E19C63.4030001@une.edu.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> "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.
>
What if the trigger is a constraint trigger that is deferred?
http://www.postgresql.org/docs/8.3/interactive/sql-createconstraint.html
klint.
--
Klint Gore
Database Manager
Sheep CRC
A.G.B.U.
University of New England
Armidale NSW 2350
Ph: 02 6773 3789
Fax: 02 6773 3266
EMail: kgore4(at)une(dot)edu(dot)au
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-19 23:55:40 | Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3 |
| Previous Message | Richard Huxton | 2008-03-19 22:40:14 | Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3 |