From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
---|---|
To: | felipe(at)informidia(dot)com(dot)br |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: When the trigger is called my application is awaiting the finish |
Date: | 2010-12-24 10:19:26 |
Message-ID: | 410676B6-EB9E-457D-A0A9-9A3F405981D0@solfertje.student.utwente.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 16 Dec 2010, at 18:13, felipe(at)informidia(dot)com(dot)br wrote:
> Hello,
> I'm having a problem running an update command that invokes a trigger, the problem is that the function performed takes about 45 minutes to finish and my application is locked waiting for the finish.
> You know how I can't wait for the end?
As usual, that depends. If running that function asynchronously from your update can not break referential integrity or cause dead-locks with your update (e.g. they aren't directly connected), then you can use LISTEN/NOTIFY to notify another process on a different connection that the function should be performed.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4d1473b6802655198511903!
From | Date | Subject | |
---|---|---|---|
Next Message | Elliot Chance | 2010-12-24 11:29:09 | Load C++ for functions? |
Previous Message | Tsutomu Nakajima | 2010-12-24 09:06:38 | did freese in creating a database cluster |